jdmeany commited on
Commit
cf5733b
·
verified ·
1 Parent(s): 8918b09

Initial test pack

Browse files

README, runs and tasks from native LayerLens records

Files changed (4) hide show
  1. .gitkeep +0 -1
  2. README.md +141 -0
  3. runs.jsonl +5 -0
  4. tasks.jsonl +1 -0
.gitkeep DELETED
@@ -1 +0,0 @@
1
- placeholder
 
 
README.md ADDED
@@ -0,0 +1,141 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-4.0
3
+ pretty_name: Gmail May Invoice Count Test
4
+ language:
5
+ - en
6
+ task_categories:
7
+ - text-generation
8
+ - question-answering
9
+ tags:
10
+ - agents
11
+ - agent-evaluation
12
+ - tool-calling
13
+ - function-calling
14
+ - email
15
+ - gmail
16
+ - accounts-payable
17
+ - invoices
18
+ - counting
19
+ - synthetic
20
+ size_categories:
21
+ - n<1K
22
+ configs:
23
+ - config_name: runs
24
+ data_files: runs.jsonl
25
+ default: true
26
+ - config_name: tasks
27
+ data_files: tasks.jsonl
28
+ ---
29
+
30
+ # Gmail May Invoice Count Test
31
+
32
+ [Blog post](https://layerlens.ai/blog/checking-vendor-identity-and-invoice-counts-in-gmail?utm_source=huggingface&utm_medium=referral&utm_campaign=test-packs&utm_content=gmail-may-invoice-count-test&utm_term=readme) | [LayerLens](https://layerlens.ai/?utm_source=huggingface&utm_medium=referral&utm_campaign=test-packs&utm_content=gmail-may-invoice-count-test&utm_term=readme)
33
+
34
+ 5 agents, each built on a different foundation model, ran once each on 1 question in a simulated Gmail inbox for an accounts payable team, the people who pay supplier bills: how many invoices are due in May 2025? The known answer is 6.
35
+
36
+ 2 of the 5 runs answered 6 and passed. 1 answered 5 and failed, and 2 returned an empty answer. The run that answered 5 searched for "2025-05", got back 12 messages in 6 threads, opened 5 of those threads and never opened the 6th, which holds INV-2025-0016 for 6,550 USD, due 2025-05-17.
37
+
38
+ The vendors, invoices and email addresses are fictional. All 5 runs happened inside LayerLens Environments, which simulates services such as Gmail so an agent can be tested on records with known answers. This pack holds the graded run records and the tool calls of the failed count, not full traces.
39
+
40
+ ## Load
41
+
42
+ ```python
43
+ from datasets import load_dataset
44
+
45
+ runs = load_dataset("LayerLens/gmail-may-invoice-count-test", "runs", split="train")
46
+ tasks = load_dataset("LayerLens/gmail-may-invoice-count-test", "tasks", split="train")
47
+ ```
48
+
49
+ ## Results
50
+
51
+ Agents are labeled A to E, with the same labels in the Gmail Same-Name Vendor Test. Foundation model names are not reported, and the results are not a ranking.
52
+
53
+ | Agent | Final answer | Grade | Trace status | Tool calls |
54
+ |---|---|---|---|---|
55
+ | Agent A | 6 | Pass | completed | 52 |
56
+ | Agent C | 6 | Pass | completed | 43 |
57
+ | Agent E | 5 | Fail | completed | 11 (10 Gmail) |
58
+ | Agent B | none | Error | error | 27 |
59
+ | Agent D | none | Fail | completed | 20 |
60
+
61
+ 2 of 5 passed, matching the task page in LayerLens (2 / 5 passed).
62
+
63
+ ## The task
64
+
65
+ > How many invoices in this mailbox are due in May 2025? Answer with the number only.
66
+
67
+ Known answer: 6. The 6 invoices, as listed in the 2 passing answers:
68
+
69
+ | Invoice | Due |
70
+ |---|---|
71
+ | INV-2025-0013 | 2025-05-01 |
72
+ | INV-2025-0014 | 2025-05-06 |
73
+ | INV-2025-0015 | 2025-05-12 |
74
+ | INV-2025-0016 | 2025-05-17 |
75
+ | INV-2025-0017 | 2025-05-23 |
76
+ | INV-2025-0018 | 2025-05-29 |
77
+
78
+ ## The environment
79
+
80
+ `gmail-ap-inbox-hard-cases`, version 1, in LayerLens Environments, task set `agg count by month`. An agent searches and reads a simulated Gmail mailbox through Gmail tools, which it looks up with a `tool_search` loader call.
81
+
82
+ ## The failed count, step by step
83
+
84
+ The Agent E run (run `may-count-e`) made 11 tool calls, 10 of them Gmail calls:
85
+
86
+ 1. `tool_search` for Gmail search tools.
87
+ 2. `gmail__search_messages` with `q: "invoice"`: estimate of 160 results.
88
+ 3. `gmail__search_messages` with `q: "\"May 2025\""`: 0 results.
89
+ 4. `gmail__search_messages` with `q: "invoice due"`: estimate of 60 results.
90
+ 5. `gmail__get_thread` on 1 thread holding INV-2025-0040.
91
+ 6. `gmail__search_messages` with `q: "\"2025-05\""`: 12 messages in 6 threads.
92
+ 7. to 11. `gmail__get_thread` on 5 of those 6 threads, holding INV-2025-0017, INV-2025-0015, INV-2025-0013, INV-2025-0018 and INV-2025-0014.
93
+
94
+ The thread it did not open holds INV-2025-0016: "Invoice INV-2025-0016 is for 6,550 USD and is due on 2025-05-17." That text comes from the same thread as read in the 2 passing runs.
95
+
96
+ Its answer:
97
+
98
+ > 5
99
+ > ANSWER: 5
100
+
101
+ The run used 77,618 tokens and cost 0.008451 USD.
102
+
103
+ ## What the grader checks and what it does not
104
+
105
+ The grader is an exact-value check on the final `ANSWER:` line against the known answer, 6. Its logged reason: `looked for "6" in the agent's final-answer line`.
106
+
107
+ It does not check:
108
+
109
+ - which invoices an agent counted. The grade depends only on the final number; the 2 passing runs happen to list the 6 invoices above.
110
+ - why a run stopped. The trace shows which thread the failed run skipped, not why; the traces hold tool calls and results, not reasoning.
111
+ - why 2 runs returned nothing. Neither empty trace holds a cost-cap or stop event, so the cause is not recorded.
112
+
113
+ ## Reproduce on LayerLens
114
+
115
+ In LayerLens Environments, open `gmail-ap-inbox-hard-cases` version 1, task set `agg count by month`, and run the task on an agent. Each attempt is graded by the exact-value check and saved as a trace with its tool calls. Whether this environment is open to accounts outside the LayerLens team is a Marin question.
116
+
117
+ ## Limitations
118
+
119
+ - 5 runs, 1 per agent, on 1 question. The pack does not show how often any foundation model answers this way.
120
+ - The 6-invoice list comes from the 2 passing answers, which agree with the known answer of 6; the pack holds no separate invoice table from the environment.
121
+ - Tool calls are listed for the failed count only. The counts for the other 4 runs were transcribed from the records without saying whether they include tool-search loader calls.
122
+ - Cost is in the pack for 3 runs: 0.008451 USD for the failed count, 0.41473 USD and 0.2890725 USD for the 2 empty answers.
123
+ - These runs happened inside the LayerLens product and cannot be rerun from this pack.
124
+
125
+ ## Files
126
+
127
+ | File | Contents |
128
+ |---|---|
129
+ | `runs.jsonl` | 1 row per run: run key, agent label, final answer, grade, trace status, tool calls, cost where recorded |
130
+ | `tasks.jsonl` | The task, the known answer, the grader and the 6 invoices listed in the passing answers |
131
+
132
+ ## Citation
133
+
134
+ ```bibtex
135
+ @misc{layerlens2026gmailmaycount,
136
+ title = {Gmail May Invoice Count Test},
137
+ author = {{LayerLens}},
138
+ year = {2026},
139
+ howpublished = {\url{https://huggingface.co/datasets/LayerLens/gmail-may-invoice-count-test}}
140
+ }
141
+ ```
runs.jsonl ADDED
@@ -0,0 +1,5 @@
 
 
 
 
 
 
1
+ {"run_key": "may-count-a", "task_id": "may-2025-invoice-count", "agent": "Agent A", "answer_line": "6", "answer": null, "passed": true, "verdict": "pass", "trace_status": "completed", "tool_calls": 52, "tool_calls_note": "count as transcribed in the 3 Nov snapshot; whether it includes tool_search loader calls is not recorded", "gmail_tool_calls": null, "key_tool_calls": null, "cost_usd": null}
2
+ {"run_key": "may-count-c", "task_id": "may-2025-invoice-count", "agent": "Agent C", "answer_line": "6", "answer": null, "passed": true, "verdict": "pass", "trace_status": "completed", "tool_calls": 43, "tool_calls_note": "count as transcribed in the 3 Nov snapshot; whether it includes tool_search loader calls is not recorded", "gmail_tool_calls": null, "key_tool_calls": null, "cost_usd": null}
3
+ {"run_key": "may-count-e", "task_id": "may-2025-invoice-count", "agent": "Agent E", "answer_line": "5", "answer": "5\nANSWER: 5", "passed": false, "verdict": "fail", "trace_status": "completed", "tool_calls": 11, "gmail_tool_calls": 10, "tool_calls_note": "11 tool.call events: 10 Gmail calls and 1 tool_search loader call; the run panel shows 10", "key_tool_calls": [{"tool": "tool_search", "args": {"limit": 5, "query": "gmail search messages by invoice due date May 2025"}}, {"tool": "gmail__search_messages", "args": {"q": "invoice", "maxResults": 100}, "resultSizeEstimate": 160}, {"tool": "gmail__search_messages", "args": {"q": "\"May 2025\"", "maxResults": 100}, "resultSizeEstimate": 0}, {"tool": "gmail__search_messages", "args": {"q": "invoice due", "maxResults": 100}, "resultSizeEstimate": 60}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000164"}, "invoices": ["INV-2025-0040"]}, {"tool": "gmail__search_messages", "args": {"q": "\"2025-05\"", "maxResults": 100}, "resultSizeEstimate": 12, "threads": ["zzz0000000000076", "zzz0000000000071", "zzz0000000000063", "zzz0000000000068", "zzz0000000000055", "zzz0000000000060"]}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000071"}, "invoices": ["INV-2025-0017"]}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000063"}, "invoices": ["INV-2025-0015"]}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000055"}, "invoices": ["INV-2025-0013"]}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000076"}, "invoices": ["INV-2025-0018"]}, {"tool": "gmail__get_thread", "args": {"id": "zzz0000000000060"}, "invoices": ["INV-2025-0014"]}], "threads_returned_by_2025_05_search": 6, "threads_opened_from_that_search": 5, "thread_not_opened": "zzz0000000000068", "invoice_in_thread_not_opened": "INV-2025-0016, 6,550 USD, Northgate Logistics Group, due 2025-05-17", "tokens_total": 77618, "cost_usd": 0.008451, "grading_evidence_text": "looked for \"6\" in the agent's final-answer line"}
4
+ {"run_key": "may-count-b", "task_id": "may-2025-invoice-count", "agent": "Agent B", "answer_line": null, "answer": "", "passed": false, "verdict": "error", "trace_status": "error", "tool_calls": 27, "tool_calls_note": "count as transcribed in the 3 Nov snapshot; whether it includes tool_search loader calls is not recorded", "gmail_tool_calls": null, "key_tool_calls": null, "cost_usd": 0.41473, "stop_event_found": false}
5
+ {"run_key": "may-count-d", "task_id": "may-2025-invoice-count", "agent": "Agent D", "answer_line": null, "answer": "", "passed": false, "verdict": "fail", "trace_status": "completed", "tool_calls": 20, "tool_calls_note": "count as transcribed in the 3 Nov snapshot; whether it includes tool_search loader calls is not recorded", "gmail_tool_calls": null, "key_tool_calls": null, "cost_usd": 0.2890725, "stop_event_found": false}
tasks.jsonl ADDED
@@ -0,0 +1 @@
 
 
1
+ {"task_id": "may-2025-invoice-count", "task_set": "agg count by month", "environment": "gmail-ap-inbox-hard-cases, version 1 (simulated Gmail, LayerLens Environments)", "prompt": "How many invoices in this mailbox are due in May 2025? Answer with the number only.", "expected_answer": "6", "grader_type": "exact value on the final ANSWER line", "grader_evidence_text": "looked for \"6\" in the agent's final-answer line", "invoices_due_in_may_from_passing_answers": {"INV-2025-0013": "2025-05-01", "INV-2025-0014": "2025-05-06", "INV-2025-0015": "2025-05-12", "INV-2025-0016": "2025-05-17", "INV-2025-0017": "2025-05-23", "INV-2025-0018": "2025-05-29"}, "runs_in_task_drawer": 5, "drawer_pass_count": "2 / 5 passed"}