When the user asks how to do something with NumbersGame, QuickBooks or Xero, or asks what to do about a problem (not when they ask you to run a job), call search_help first. Answer from the article it finds (get_help_article reads one in full): quote its example prompt where it has one and give the user its url. If nothing matched, say so rather than inventing steps. A company id (realm_id) comes from the project's company file, from list_companies, or from the user; never guess one. Writes are capped at 50 a minute per company, under the ledger's own limit (Xero allows 60 calls a minute per organisation): run single-record write loops one at a time, not in parallel, at that pace or slower, and use a bulk tool where one exists.
Discoverability
0/6 passed0 of 6 passed0/100
Client listings and public setup information.
mcp.json or server-card.json
Either mcp.json or an MCP Server Card declaring this endpoint passes.
No matching mcp.json manifest or MCP Server Card was found at the checked URLs.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a customer in QuickBooks Online, or a contact in Xero. On Xero this creates a Contact: Xero keeps ONE contact record for customers and vendors and marks it a customer only once an invoice is raised against it, so what this creates is indistinguishable from what create_vendor creates. Xero has a single Name field, so DisplayName and CompanyName cannot both be kept - sending two different values is refused rather than losing one. Notes has no Xero home and is refused rather than dropped. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Customer with "created": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_customer applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).
The description explains the capability, when to use it, and what to expect.
Inputs19/100
2 of 9 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer › DisplayName
Customer display name (required, must be unique). On Xero this becomes the contact's single Name; do not also send a different CompanyName, which is refused rather than dropped. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › customer › GivenName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › FamilyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › CompanyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › BillAddr
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › Notes
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_customer",
"title": "Create Customer",
"description": "Create a customer in QuickBooks Online, or a contact in Xero. On Xero this creates a Contact: Xero keeps ONE contact record for customers and vendors and marks it a customer only once an invoice is raised against it, so what this creates is indistinguishable from what create_vendor creates. Xero has a single Name field, so DisplayName and CompanyName cannot both be kept - sending two different values is refused rather than losing one. Notes has no Xero home and is refused rather than dropped. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Customer with \"created\": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_customer applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"realm_id"
],
"properties": {
"customer": {
"type": "object",
"required": [
"DisplayName"
],
"properties": {
"Notes": {
"type": "string",
"maxLength": 2000
},
"BillAddr": {},
"GivenName": {
"type": "string",
"maxLength": 100
},
"FamilyName": {
"type": "string",
"maxLength": 100
},
"CompanyName": {
"type": "string",
"maxLength": 500
},
"DisplayName": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Customer display name (required, must be unique). On Xero this becomes the contact's single Name; do not also send a different CompanyName, which is refused rather than dropped. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"required": [
"FreeFormNumber"
],
"properties": {
"FreeFormNumber": {
"type": "string"
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"required": [
"Address"
],
"properties": {
"Address": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Customer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Get a customer by Id from QuickBooks Online or Xero. On Xero this reads Contacts/{id} - the SAME record get_vendor reads, because Xero keeps one contact record and does not distinguish customers from vendors. Xero derives the role from the documents posted against the contact, so nothing on the returned record confirms it is a customer. For several customers, use one search_customers call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_customer calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_customer",
"title": "Get Customer",
"description": "Get a customer by Id from QuickBooks Online or Xero. On Xero this reads Contacts/{id} - the SAME record get_vendor reads, because Xero keeps one contact record and does not distinguish customers from vendors. Xero derives the role from the documents posted against the contact, so nothing on the returned record confirms it is a customer. For several customers, use one search_customers call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_customer calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Customer",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Update an existing customer in QuickBooks Online or Xero. Xero holds one contact record for customers and suppliers, so this edits the same record update_vendor does; it has a single Name rather than separate display and company names, and phone numbers and addresses are merged by type rather than replaced. Archiving a Xero contact that still has money owed on either side needs confirm_archive: true, and Xero's API cannot restore an archived contact. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).
The description explains the capability, when to use it, and what to expect.
Inputs34/100
5 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer › Id
QBO Customer ID
Resolve the mismatch between this description and its schema constraints.
params › customer › SyncToken
QuickBooks optimistic-concurrency token, from the record you are updating. REQUIRED for QuickBooks companies. Xero has no equivalent and refuses it — omit it there; concurrent Xero updates are last-writer-wins.
Clear enough to supply this argument.
params › customer › DisplayName
Customer display name; must stay unique across the shared name list. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › customer › GivenName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › FamilyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › CompanyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › Active
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › customer › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_archive
Xero only; ignored on QuickBooks. Archiving a Xero contact (Active: false, or ContactStatus ARCHIVED) that still has money owed on either side -- unpaid invoices or unpaid bills -- needs confirm_archive: true, on the first call, once the user has agreed. Xero keeps one record for customer and supplier, so the archive covers both, and Xero's API cannot restore an archived contact: only a person in Xero can.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_customer",
"title": "Update Customer",
"description": "Update an existing customer in QuickBooks Online or Xero. Xero holds one contact record for customers and suppliers, so this edits the same record update_vendor does; it has a single Name rather than separate display and company names, and phone numbers and addresses are merged by type rather than replaced. Archiving a Xero contact that still has money owed on either side needs confirm_archive: true, and Xero's API cannot restore an archived contact. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"realm_id"
],
"properties": {
"customer": {
"type": "object",
"required": [
"Id"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Customer ID"
},
"Active": {
"type": "boolean"
},
"GivenName": {
"type": "string",
"maxLength": 100
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "QuickBooks optimistic-concurrency token, from the record you are updating. REQUIRED for QuickBooks companies. Xero has no equivalent and refuses it — omit it there; concurrent Xero updates are last-writer-wins."
},
"FamilyName": {
"type": "string",
"maxLength": 100
},
"CompanyName": {
"type": "string",
"maxLength": 500
},
"DisplayName": {
"type": "string",
"maxLength": 500,
"description": "Customer display name; must stay unique across the shared name list. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"required": [
"FreeFormNumber"
],
"properties": {
"FreeFormNumber": {
"type": "string",
"maxLength": 30
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"required": [
"Address"
],
"properties": {
"Address": {
"type": "string",
"maxLength": 100
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"confirm_archive": {
"type": "boolean",
"description": "Xero only; ignored on QuickBooks. Archiving a Xero contact (Active: false, or ContactStatus ARCHIVED) that still has money owed on either side -- unpaid invoices or unpaid bills -- needs confirm_archive: true, on the first call, once the user has agreed. Xero keeps one record for customer and supplier, so the archive covers both, and Xero's API cannot restore an archived contact: only a person in Xero can."
}
}
}
}
},
"annotations": {
"title": "Update Customer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
Align the title with the capability actually described by this tool.
Description87/100
Search customers in QuickBooks Online, or contacts in Xero, that match given criteria. On Xero this reads the Contacts endpoint, and Xero keeps ONE contact record: customers and vendors are the same record there, so search_vendors returns those same rows and nothing here selects customers specifically. DisplayName and CompanyName both map to Xero's single Name field. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. Active filters on ACTIVE vs ARCHIVED contact status and must be true or false. Balance, MiddleName, PrintOnCheckName, BillRate, Job, BalanceWithJobs and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Customer entity. One of: Id, DisplayName, GivenName, FamilyName, CompanyName, PrimaryEmailAddr, Balance, Active, MetaData.CreateTime, MetaData.LastUpdatedTime, Job, BalanceWithJobs. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Customer entity. One of: Id, DisplayName, GivenName, FamilyName, CompanyName, PrimaryEmailAddr, Balance, Active, MetaData.CreateTime, MetaData.LastUpdatedTime, Job, BalanceWithJobs. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_customers",
"title": "Search Customers",
"description": "Search customers in QuickBooks Online, or contacts in Xero, that match given criteria. On Xero this reads the Contacts endpoint, and Xero keeps ONE contact record: customers and vendors are the same record there, so search_vendors returns those same rows and nothing here selects customers specifically. DisplayName and CompanyName both map to Xero's single Name field. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. Active filters on ACTIVE vs ARCHIVED contact status and must be true or false. Balance, MiddleName, PrintOnCheckName, BillRate, Job, BalanceWithJobs and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"enum": [
"Id",
"DisplayName",
"CompanyName",
"Balance",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime"
],
"type": "string"
},
"desc": {
"enum": [
"Id",
"DisplayName",
"CompanyName",
"Balance",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime"
],
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Customer entity. One of: Id, DisplayName, GivenName, FamilyName, CompanyName, PrimaryEmailAddr, Balance, Active, MetaData.CreateTime, MetaData.LastUpdatedTime, Job, BalanceWithJobs. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
},
"additionalProperties": false
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Customer entity. One of: Id, DisplayName, GivenName, FamilyName, CompanyName, PrimaryEmailAddr, Balance, Active, MetaData.CreateTime, MetaData.LastUpdatedTime, Job, BalanceWithJobs. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
},
"additionalProperties": false
}
]
},
"maxItems": 20,
"description": "Filters to apply. Unknown fields are rejected instead of silently broadening the query. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Search Customers",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Create an estimate in QuickBooks Online: a quote for a customer that posts nothing to the ledger until it is accepted and turned into an invoice. Lines and header pass through to QuickBooks unchanged, so class and department tracking work - ClassRef INSIDE each line's SalesItemLineDetail object, DepartmentRef on the DOCUMENT and never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010) - and TxnTaxDetail passes through for companies with sales tax enabled - prefer setting TaxCodeRef per line and letting QuickBooks calculate the tax. Use search_estimates to find one and update_estimate to correct it.On Xero this writes a Quote, the closest like-for-like mapping in this integration. It is created as a DRAFT: a QuickBooks estimate is a proposal with no ledger effect, and Xero's SENT and ACCEPTED are states a person moves it to - creating one already SENT would claim a customer had been shown it. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs13/100
1 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › estimate › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › Line
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › ExpirationDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_estimate",
"title": "Create Estimate",
"description": "Create an estimate in QuickBooks Online: a quote for a customer that posts nothing to the ledger until it is accepted and turned into an invoice. Lines and header pass through to QuickBooks unchanged, so class and department tracking work - ClassRef INSIDE each line's SalesItemLineDetail object, DepartmentRef on the DOCUMENT and never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010) - and TxnTaxDetail passes through for companies with sales tax enabled - prefer setting TaxCodeRef per line and letting QuickBooks calculate the tax. Use search_estimates to find one and update_estimate to correct it.On Xero this writes a Quote, the closest like-for-like mapping in this integration. It is created as a DRAFT: a QuickBooks estimate is a proposal with no ledger effect, and Xero's SENT and ACCEPTED are states a person moves it to - creating one already SENT would claim a customer had been shown it. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"estimate",
"realm_id"
],
"properties": {
"estimate": {
"type": "object",
"required": [
"CustomerRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"ExpirationDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Estimate",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Get an estimate by Id from QuickBooks Online.On Xero this reads one Quote. For several estimates, use one search_estimates call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_estimate calls in parallel, which QuickBooks rate-limits (code 3001).
Describe the returned information so the agent knows whether it will answer the request.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_estimate",
"title": "Get Estimate",
"description": "Get an estimate by Id from QuickBooks Online.On Xero this reads one Quote. For several estimates, use one search_estimates call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_estimate calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Estimate",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Update an estimate in QuickBooks Online by Id. Requires Id and SyncToken (get both from get_estimate or search_estimates). Lines and header pass through unchanged, so ClassRef, DepartmentRef and TxnTaxDetail all work - ClassRef INSIDE each line's SalesItemLineDetail object, DepartmentRef on the DOCUMENT and never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). Sending Line replaces every line on the estimate, so send them all, not just the one you are changing.On Xero this updates the Quote. Id is required; SyncToken is ignored (Xero has none). Sending Line REPLACES every line, and an empty list is refused rather than emptying the document. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs20/100
3 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › estimate › Id
QBO Estimate ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › estimate › SyncToken
Optimistic concurrency token
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › estimate › Line
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › ExpirationDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › estimate › TxnStatus
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_estimate",
"title": "Update Estimate",
"description": "Update an estimate in QuickBooks Online by Id. Requires Id and SyncToken (get both from get_estimate or search_estimates). Lines and header pass through unchanged, so ClassRef, DepartmentRef and TxnTaxDetail all work - ClassRef INSIDE each line's SalesItemLineDetail object, DepartmentRef on the DOCUMENT and never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). Sending Line replaces every line on the estimate, so send them all, not just the one you are changing.On Xero this updates the Quote. Id is required; SyncToken is ignored (Xero has none). Sending Line REPLACES every line, and an empty list is refused rather than emptying the document. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"estimate",
"realm_id"
],
"properties": {
"estimate": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Estimate ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token"
},
"TxnStatus": {
"type": "string"
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"ExpirationDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Update Estimate",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description73/100
Search estimates in QuickBooks Online that match given criteria.On Xero this reads Quotes -- the closest like-for-like mapping in this integration. Filter on Id, DocNumber (QuoteNumber), TxnDate, ExpirationDate (ExpiryDate) or TotalAmt.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Estimate entity. One of: Id, DocNumber, TxnDate, CustomerRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. Defaults to '=' if omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Estimate entity. One of: Id, DocNumber, TxnDate, CustomerRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_estimates",
"title": "Search Estimates",
"description": "Search estimates in QuickBooks Online that match given criteria.On Xero this reads Quotes -- the closest like-for-like mapping in this integration. Filter on Id, DocNumber (QuoteNumber), TxnDate, ExpirationDate (ExpiryDate) or TotalAmt.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Estimate entity. One of: Id, DocNumber, TxnDate, CustomerRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"enum": [
"=",
"<",
">",
"<=",
">=",
"LIKE",
"IN"
],
"type": "string",
"description": "Comparison operator. Defaults to '=' if omitted."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Estimate entity. One of: Id, DocNumber, TxnDate, CustomerRef, TotalAmt, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use the advanced form {field,value,operator?} for operators or the simple {key,value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Estimates",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Create an accounts payable bill in QuickBooks Online: an expense owed to a vendor and payable later. Use it when an invoice arrives before the money leaves. If the money already left the account, record it with create_purchase instead. Settle a bill with create_bill_payment, never by posting a second expense. On QuickBooks each Line also accepts ClassRef for class tracking, CustomerRef and BillableStatus for billable costs, and TaxCodeRef for tax - all INSIDE the line's own AccountBasedExpenseLineDetail object, next to AccountRef. DepartmentRef is a DOCUMENT-level field: put it on the bill, never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). On Xero a line ClassRef IS mapped: its value is a tracking option's id or name (search_classes), in either of the organisation's tracking categories. Xero has no departments and no billable-expense passthrough, so DepartmentRef, CustomerRef and BillableStatus are REFUSED with a reason rather than posting the bill without them. Xero DOES take CurrencyRef, PrivateNote or Memo, and a line TaxCodeRef, which are mapped. TO CREATE MORE THAN ONE BILL, PASS THEM ALL IN `bills` RATHER THAN CALLING THIS TOOL REPEATEDLY: on Xero a batch of 50 costs ONE API call against a hard 5,000-per-day-per-company ceiling that no plan lifts, so 500 bills sent one at a time spend 10% of the company's day and the same 500 sent as `bills` spend 0.2%. Each row comes back with its own outcome, because some can be rejected while the rest are created. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does. A company that pays its bills through BILL (Bill.com) gets its bills from BILL's sync: enter such a bill in BILL rather than here, or it is booked twice once BILL syncs. Use this tool for bills that are not in BILL.
The description explains the capability, when to use it, and what to expect.
Inputs7/100
3 of 45 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › bill › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › DetailType
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › AccountRef › value
The expense account's Id -- a short numeric string such as "21" -- and NEVER its name: the account name here is refused as "Invalid Number" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts.
Clear enough to supply this argument.
params › bill › Line › items › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DueDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › CurrencyRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › CurrencyRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SalesTermRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SalesTermRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Balance
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › bills › items › Line › items › AccountRef › value
The expense account's Id -- a short numeric string such as "21" -- and NEVER its name: the account name here is refused as "Invalid Number" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts.
Clear enough to supply this argument.
params › bills › items › Line › items › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › DueDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › Memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › CurrencyRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › CurrencyRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › SalesTermRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › SalesTermRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › Balance
Not provided
Missing description. Explain what this value means and how to supply it.
params › bills › items › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_bill",
"title": "Create Bill",
"description": "Create an accounts payable bill in QuickBooks Online: an expense owed to a vendor and payable later. Use it when an invoice arrives before the money leaves. If the money already left the account, record it with create_purchase instead. Settle a bill with create_bill_payment, never by posting a second expense. On QuickBooks each Line also accepts ClassRef for class tracking, CustomerRef and BillableStatus for billable costs, and TaxCodeRef for tax - all INSIDE the line's own AccountBasedExpenseLineDetail object, next to AccountRef. DepartmentRef is a DOCUMENT-level field: put it on the bill, never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). On Xero a line ClassRef IS mapped: its value is a tracking option's id or name (search_classes), in either of the organisation's tracking categories. Xero has no departments and no billable-expense passthrough, so DepartmentRef, CustomerRef and BillableStatus are REFUSED with a reason rather than posting the bill without them. Xero DOES take CurrencyRef, PrivateNote or Memo, and a line TaxCodeRef, which are mapped. TO CREATE MORE THAN ONE BILL, PASS THEM ALL IN `bills` RATHER THAN CALLING THIS TOOL REPEATEDLY: on Xero a batch of 50 costs ONE API call against a hard 5,000-per-day-per-company ceiling that no plan lifts, so 500 bills sent one at a time spend 10% of the company's day and the same 500 sent as `bills` spend 0.2%. Each row comes back with its own outcome, because some can be rejected while the rest are created. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does. A company that pays its bills through BILL (Bill.com) gets its bills from BILL's sync: enter such a bill in BILL rather than here, or it is booked twice once BILL syncs. Use this tool for bills that are not in BILL.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"bill": {
"type": "object",
"required": [
"Line",
"VendorRef",
"DueDate"
],
"properties": {
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"DetailType",
"Description",
"AccountRef"
],
"properties": {
"Amount": {
"type": "number"
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"description": "The expense account's Id -- a short numeric string such as \"21\" -- and NEVER its name: the account name here is refused as \"Invalid Number\" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts."
}
}
},
"DetailType": {
"type": "string"
},
"Description": {
"type": "string"
}
},
"additionalProperties": {}
}
},
"Memo": {
"type": "string"
},
"Balance": {
"type": "number"
},
"DueDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"CurrencyRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"PrivateNote": {
"type": "string"
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"SalesTermRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
}
},
"additionalProperties": {}
},
"bills": {
"type": "array",
"items": {
"type": "object",
"required": [
"Line",
"VendorRef",
"DueDate"
],
"properties": {
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"DetailType",
"Description",
"AccountRef"
],
"properties": {
"Amount": {
"type": "number"
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"description": "The expense account's Id -- a short numeric string such as \"21\" -- and NEVER its name: the account name here is refused as \"Invalid Number\" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts."
}
}
},
"DetailType": {
"type": "string"
},
"Description": {
"type": "string"
}
},
"additionalProperties": {}
}
},
"Memo": {
"type": "string"
},
"Balance": {
"type": "number"
},
"DueDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"CurrencyRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"PrivateNote": {
"type": "string"
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"SalesTermRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
}
},
"additionalProperties": {}
}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Bill",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Update a bill in QuickBooks Online, or a supplier bill (ACCPAY) in Xero. Supports sparse updates - only the fields you supply are changed. Id is always required. SyncToken is required for QuickBooks (fetch it via get_bill or search_bills first); Xero has no SyncToken, ignores one if sent, and is last-writer-wins on concurrent updates. On Xero: invoices and bills share one endpoint, so passing a customer invoice id here is refused by name rather than rewriting the invoice; a VOIDED or DELETED bill is refused with its status. A PAID bill can still be edited on Xero: every header field is accepted, and a line can be moved to a different account by sending that line back with the LineItemID from get_bill - no need to remove or reverse the payment, and it stays reconciled. Sending Line WITHOUT LineItemIDs replaces the whole line set and is refused while the bill is paid; on an unpaid bill it replaces the lines and changes their ids. Xero cannot blank a field - set it to its new value instead. A line ClassRef sets a Xero tracking option (id or name, from search_classes) on that line and keeps the line's tag in the other tracking category; a line sent back with its LineItemID and no ClassRef keeps the tracking it has. Departments, billable expenses and TaxCodeRef-by-id have no Xero equivalent and are refused by name. ClassRef, CustomerRef and BillableStatus go INSIDE each line's AccountBasedExpenseLineDetail object, next to AccountRef. DepartmentRef is a DOCUMENT-level field: put it on the bill, never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). Sending Line replaces the whole line set, so send every line you want to keep. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does.
The description explains the capability, when to use it, and what to expect.
Inputs8/100
2 of 25 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › bill › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SyncToken
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › DetailType
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Line › items › AccountRef › value
The expense account's Id -- a short numeric string such as "21" -- and NEVER its name: the account name here is refused as "Invalid Number" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts.
Clear enough to supply this argument.
params › bill › Line › items › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DueDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › CurrencyRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › CurrencyRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SalesTermRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SalesTermRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › Balance
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_bill",
"title": "Update Bill",
"description": "Update a bill in QuickBooks Online, or a supplier bill (ACCPAY) in Xero. Supports sparse updates - only the fields you supply are changed. Id is always required. SyncToken is required for QuickBooks (fetch it via get_bill or search_bills first); Xero has no SyncToken, ignores one if sent, and is last-writer-wins on concurrent updates. On Xero: invoices and bills share one endpoint, so passing a customer invoice id here is refused by name rather than rewriting the invoice; a VOIDED or DELETED bill is refused with its status. A PAID bill can still be edited on Xero: every header field is accepted, and a line can be moved to a different account by sending that line back with the LineItemID from get_bill - no need to remove or reverse the payment, and it stays reconciled. Sending Line WITHOUT LineItemIDs replaces the whole line set and is refused while the bill is paid; on an unpaid bill it replaces the lines and changes their ids. Xero cannot blank a field - set it to its new value instead. A line ClassRef sets a Xero tracking option (id or name, from search_classes) on that line and keeps the line's tag in the other tracking category; a line sent back with its LineItemID and no ClassRef keeps the tracking it has. Departments, billable expenses and TaxCodeRef-by-id have no Xero equivalent and are refused by name. ClassRef, CustomerRef and BillableStatus go INSIDE each line's AccountBasedExpenseLineDetail object, next to AccountRef. DepartmentRef is a DOCUMENT-level field: put it on the bill, never on a line, which accepts it in neither position (measured 2026-09-10; the whole request fails with code 2010). Sending Line replaces the whole line set, so send every line you want to keep. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"bill",
"realm_id"
],
"properties": {
"bill": {
"type": "object",
"required": [
"Id"
],
"properties": {
"Id": {
"type": "string"
},
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"DetailType"
],
"properties": {
"Amount": {
"type": "number"
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"description": "The expense account's Id -- a short numeric string such as \"21\" -- and NEVER its name: the account name here is refused as \"Invalid Number\" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts."
}
}
},
"DetailType": {
"type": "string"
},
"Description": {
"type": "string"
}
},
"additionalProperties": {}
}
},
"Memo": {
"type": "string"
},
"Balance": {
"type": "number"
},
"DueDate": {
"type": "string"
},
"TxnDate": {
"type": "string"
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string"
},
"SyncToken": {
"type": "string"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"CurrencyRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"PrivateNote": {
"type": "string"
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"SalesTermRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Update Bill",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Delete a bill in QuickBooks Online, or void one in Xero. Xero keeps bills and invoices on one endpoint and does not destroy documents: an approved bill becomes VOIDED and a draft becomes DELETED, the bill number is retained either way, and a bill that has been paid is refused until the payment is reversed.
The description explains the capability, when to use it, and what to expect.
Inputs33/100
1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › bill › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › bill › SyncToken
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_bill",
"title": "Delete Bill",
"description": "Delete a bill in QuickBooks Online, or void one in Xero. Xero keeps bills and invoices on one endpoint and does not destroy documents: an approved bill becomes VOIDED and a draft becomes DELETED, the bill number is retained either way, and a bill that has been paid is refused until the payment is reversed.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"bill",
"realm_id"
],
"properties": {
"bill": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"SyncToken": {
"type": "string"
}
}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Delete Bill",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Get a supplier bill by ID from QuickBooks Online or Xero. On Xero this reads Invoices/{id}: bills and customer invoices share one endpoint there and are separated only by Type, so an invoice id passed here is refused as belonging to the other document type rather than returned as a bill. Use read_invoice for those. For several bills, use one search_bills call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_bill calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_bill",
"title": "Get Bill",
"description": "Get a supplier bill by ID from QuickBooks Online or Xero. On Xero this reads Invoices/{id}: bills and customer invoices share one endpoint there and are separated only by Type, so an invoice id passed here is refused as belonging to the other document type rather than returned as a bill. Use read_invoice for those. For several bills, use one search_bills call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_bill calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Bill",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Search bills in QuickBooks Online, or supplier bills in Xero, that match given criteria. On Xero this reads the Invoices endpoint filtered to Type ACCPAY - customer invoices sit on that same endpoint as ACCREC and the Type is the whole difference - with the QuickBooks field names translated: DocNumber to InvoiceNumber, TxnDate to Date, Balance to AmountDue, TotalAmt to Total. VendorRef is sent as Xero's ContactIDs parameter and so supports equality only. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. APAccountRef, PrivateNote, SalesTermRef and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Bill entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, TxnDate, DueDate, Balance, TotalAmt, VendorRef, APAccountRef, DocNumber, PrivateNote, SalesTermRef. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. Defaults to '=' if omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Bill entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, TxnDate, DueDate, Balance, TotalAmt, VendorRef, APAccountRef, DocNumber, PrivateNote, SalesTermRef. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_bills",
"title": "Search Bills",
"description": "Search bills in QuickBooks Online, or supplier bills in Xero, that match given criteria. On Xero this reads the Invoices endpoint filtered to Type ACCPAY - customer invoices sit on that same endpoint as ACCREC and the Type is the whole difference - with the QuickBooks field names translated: DocNumber to InvoiceNumber, TxnDate to Date, Balance to AmountDue, TotalAmt to Total. VendorRef is sent as Xero's ContactIDs parameter and so supports equality only. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. APAccountRef, PrivateNote, SalesTermRef and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Bill entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, TxnDate, DueDate, Balance, TotalAmt, VendorRef, APAccountRef, DocNumber, PrivateNote, SalesTermRef. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"enum": [
"=",
"<",
">",
"<=",
">=",
"LIKE",
"IN"
],
"type": "string",
"description": "Comparison operator. Defaults to '=' if omitted."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Bill entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, TxnDate, DueDate, Balance, TotalAmt, VendorRef, APAccountRef, DocNumber, PrivateNote, SalesTermRef. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use the advanced form {field,value,operator?} for operators or the simple {key,value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Bills",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Read a single customer invoice from QuickBooks Online or Xero by its ID. On Xero this reads Invoices/{id}: invoices and bills share one endpoint there and are separated only by Type, so a bill id passed here is refused as belonging to the other document type rather than returned as an invoice. Use get_bill for those. For several invoices, use one search_invoices call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many read_invoice calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › invoice_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "read_invoice",
"title": "Get Invoice",
"description": "Read a single customer invoice from QuickBooks Online or Xero by its ID. On Xero this reads Invoices/{id}: invoices and bills share one endpoint there and are separated only by Type, so a bill id passed here is refused as belonging to the other document type rather than returned as an invoice. Use get_bill for those. For several invoices, use one search_invoices call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many read_invoice calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"invoice_id": {
"type": "string",
"minLength": 1
}
}
}
}
},
"annotations": {
"title": "Get Invoice",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Search customer invoices in QuickBooks Online or Xero using criteria (maps to node-quickbooks findInvoices on QuickBooks). On Xero this reads the Invoices endpoint filtered to Type ACCREC - bills sit on that same endpoint as ACCPAY and the Type is the whole difference - with the QuickBooks field names translated: DocNumber to InvoiceNumber, TxnDate to Date, Balance to AmountDue, TotalAmt to Total. CustomerRef is sent as Xero's ContactIDs parameter and so supports equality only. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. ClassRef, SalesTermRef, EInvoiceStatus and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped.
The description explains the capability, when to use it, and what to expect.
Inputs19/100
6 of 31 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › anyOf › 0 › Id
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › DueDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › CustomerRef
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › ClassRef
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › Balance
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 0 › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored.
Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored.
Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored.
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › anyOf › 2 › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_invoices",
"title": "Search Invoices",
"description": "Search customer invoices in QuickBooks Online or Xero using criteria (maps to node-quickbooks findInvoices on QuickBooks). On Xero this reads the Invoices endpoint filtered to Type ACCREC - bills sit on that same endpoint as ACCPAY and the Type is the whole difference - with the QuickBooks field names translated: DocNumber to InvoiceNumber, TxnDate to Date, Balance to AmountDue, TotalAmt to Total. CustomerRef is sent as Xero's ContactIDs parameter and so supports equality only. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. ClassRef, SalesTermRef, EInvoiceStatus and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"criteria": {
"anyOf": [
{
"type": "object",
"properties": {
"Id": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"asc": {
"enum": [
"Id",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime",
"DocNumber",
"TxnDate",
"DueDate",
"Balance",
"TotalAmt"
],
"type": "string"
},
"desc": {
"enum": [
"Id",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime",
"DocNumber",
"TxnDate",
"DueDate",
"Balance",
"TotalAmt"
],
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"Balance": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"DueDate": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"TxnDate": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"ClassRef": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"TotalAmt": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"DocNumber": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"CustomerRef": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"MetaData.CreateTime": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"MetaData.LastUpdatedTime": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
},
"additionalProperties": false
},
{
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"enum": [
"=",
"IN",
"<",
">",
"<=",
">=",
"LIKE"
],
"type": "string"
}
},
"additionalProperties": false
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
},
"additionalProperties": false
}
]
},
"maxItems": 20
},
{
"type": "object",
"properties": {
"asc": {
"enum": [
"Id",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime",
"DocNumber",
"TxnDate",
"DueDate",
"Balance",
"TotalAmt"
],
"type": "string"
},
"desc": {
"enum": [
"Id",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime",
"DocNumber",
"TxnDate",
"DueDate",
"Balance",
"TotalAmt"
],
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"filters": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Invoice entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, DocNumber, TxnDate, DueDate, CustomerRef, ClassRef, Balance, TotalAmt, SalesTermRef, EInvoiceStatus. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"enum": [
"=",
"IN",
"<",
">",
"<=",
">=",
"LIKE"
],
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 20
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
}
},
"additionalProperties": false
}
],
"description": "Invoice filters. Unknown fields are rejected instead of silently broadening the query. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Invoices",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Create an invoice in QuickBooks Online or Xero. On Xero due_date is REQUIRED - Xero rejects an invoice without one, and guessing a payment term would move the invoice into the wrong aging bucket - and the invoice is created AUTHORISED rather than as a Xero draft, so it reaches AR aging the way a QuickBooks create does. Xero lines address an item by its Code, so item ids are resolved to codes for you, and line amounts are sent tax-exclusive. Xero tracks by category NAME rather than by id, so class_ref and department_ref are refused rather than posted to the wrong dimension. Tax is set PER LINE with line_items[].tax_code_ref: a QuickBooks company outside the US (GST/HST, VAT) needs one on every line; get_ledger_settings lists the company's tax_codes. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs21/100
4 of 14 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › item_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › qty
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › unit_price
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › class_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › tax_code_ref
Tax code for this line. QuickBooks outside the US (GST/HST, VAT): a TaxCode id from get_ledger_settings' tax_codes, required on every line. QuickBooks US: TAX or NON. Xero: the TaxType, e.g. OUTPUT2; omitted, Xero applies the account's default.
Resolve the mismatch between this description and its schema constraints.
params › doc_number
Not provided
Missing description. Explain what this value means and how to supply it.
params › txn_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › due_date
Due date in YYYY-MM-DD. Optional on QuickBooks (the customer's terms apply). REQUIRED for Xero companies.
Clear enough to supply this argument.
params › class_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › department_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › tax_detail
QuickBooks TxnTaxDetail, passed through unchanged (its code field is TxnTaxCodeRef, US sales tax only). A tax code for the lines goes in line_items[].tax_code_ref, not here.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_invoice",
"title": "Create Invoice",
"description": "Create an invoice in QuickBooks Online or Xero. On Xero due_date is REQUIRED - Xero rejects an invoice without one, and guessing a payment term would move the invoice into the wrong aging bucket - and the invoice is created AUTHORISED rather than as a Xero draft, so it reaches AR aging the way a QuickBooks create does. Xero lines address an item by its Code, so item ids are resolved to codes for you, and line amounts are sent tax-exclusive. Xero tracks by category NAME rather than by id, so class_ref and department_ref are refused rather than posted to the wrong dimension. Tax is set PER LINE with line_items[].tax_code_ref: a QuickBooks company outside the US (GST/HST, VAT) needs one on every line; get_ledger_settings lists the company's tax_codes. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer_ref",
"line_items",
"realm_id"
],
"properties": {
"due_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Due date in YYYY-MM-DD. Optional on QuickBooks (the customer's terms apply). REQUIRED for Xero companies."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"txn_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"class_ref": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"doc_number": {
"type": "string"
},
"line_items": {
"type": "array",
"items": {
"type": "object",
"required": [
"item_ref",
"qty",
"unit_price"
],
"properties": {
"qty": {
"type": "number",
"exclusiveMinimum": 0
},
"item_ref": {
"type": "string",
"minLength": 1
},
"class_ref": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"unit_price": {
"type": "number",
"minimum": 0
},
"description": {
"type": "string"
},
"tax_code_ref": {
"type": "string",
"maxLength": 50,
"minLength": 1,
"description": "Tax code for this line. QuickBooks outside the US (GST/HST, VAT): a TaxCode id from get_ledger_settings' tax_codes, required on every line. QuickBooks US: TAX or NON. Xero: the TaxType, e.g. OUTPUT2; omitted, Xero applies the account's default."
}
}
},
"minItems": 1
},
"tax_detail": {
"type": "object",
"properties": {},
"description": "QuickBooks TxnTaxDetail, passed through unchanged (its code field is TxnTaxCodeRef, US sales tax only). A tax code for the lines goes in line_items[].tax_code_ref, not here.",
"additionalProperties": {}
},
"customer_ref": {
"type": "string",
"minLength": 1
},
"department_ref": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
}
},
"annotations": {
"title": "Create Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Update an existing invoice in Quickbooks by ID (sparse update). On Xero, supplying lines WITHOUT their LineItemID REPLACES every line on the document and Xero reassigns their ids, which breaks any payment or credit-note allocation against the old ones - so send the full set you want to end up with, and omit lines entirely when you only mean to change a header field. A PAID invoice is still editable on Xero: every header field is accepted, and a line can be moved to a different account by sending that line back with the LineItemID from read_invoice - no need to remove or reverse the payment, and it stays reconciled. Lines sent without LineItemIDs are refused while the invoice is paid, because those replace the line set. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
2 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › invoice_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › patch
Not provided
Missing description. Explain what this value means and how to supply it.
params › clear_fields
Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_invoice",
"title": "Update Invoice",
"description": "Update an existing invoice in Quickbooks by ID (sparse update). On Xero, supplying lines WITHOUT their LineItemID REPLACES every line on the document and Xero reassigns their ids, which breaks any payment or credit-note allocation against the old ones - so send the full set you want to end up with, and omit lines entirely when you only mean to change a header field. A PAID invoice is still editable on Xero: every header field is accepted, and a line can be moved to a different account by sending that line back with the LineItemID from read_invoice - no need to remove or reverse the payment, and it stays reconciled. Lines sent without LineItemIDs are refused while the invoice is paid, because those replace the line set. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice_id",
"patch",
"realm_id"
],
"properties": {
"patch": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"invoice_id": {
"type": "string",
"minLength": 1
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken."
}
}
}
}
},
"annotations": {
"title": "Update Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Create a new account in the QuickBooks Online or Xero chart of accounts (COA). Use to add a general ledger account - expense, income, asset, liability, or equity account - when classifying transactions needs an account that does not yet exist. On Xero acct_num is REQUIRED and becomes the account Code that every Xero bill line addresses. A Xero BANK account cannot be created here: Xero requires the bank account number and NumbersGame does not handle bank account numbers, so tell the user to add it in Xero (Accounting > Chart of accounts > Add Bank Account); once it exists it is used here as normal. Xero has a single account type from its own vocabulary (EXPENSE, REVENUE, CURRENT, FIXED, and so on) rather than a type plus a sub_type, so sub_type is refused there rather than dropped. Xero's chart of accounts has no parent/child hierarchy, so there are no sub-accounts to create. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Account with "created": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_account applies it if you want it. It still refuses when the record holding the name is inactive, since an inactive record cannot be used on a document.
The description explains the capability, when to use it, and what to expect.
Inputs54/100
4 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › acct_num
Account number/code. Optional on QuickBooks. REQUIRED for Xero companies, where every bill line refers to it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › type
On QuickBooks: AccountType, in spaced title case, one of: Accounts Payable, Accounts Receivable, Bank, Cost of Goods Sold, Credit Card, Equity, Expense, Fixed Asset, Income, Long Term Liability, Other Asset, Other Current Asset, Other Current Liability, Other Expense, Other Income. On Xero this is Xero's own single account type instead (EXPENSE, REVENUE, CURRENT, FIXED, ...), and sub_type must be omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sub_type
QuickBooks only; omit on Xero. AccountSubType, in spaceless PascalCase -- the casing differs from type, which is spaced. Supply it for an Equity account: omitting it makes QuickBooks default to OpeningBalanceEquity, of which a company may have only one, so the create fails with 'There can be only one account of detail type Opening Balance Equity'. Values seen in live companies, by type (examples, not an exhaustive list -- QuickBooks accepts others): Accounts Payable: AccountsPayable | Accounts Receivable: AccountsReceivable | Bank: CashOnHand, Checking, MoneyMarket, Savings, TrustAccounts | Cost of Goods Sold: CostOfLaborCos, EquipmentRentalCos, OtherCostsOfServiceCos, ShippingFreightDeliveryCos, SuppliesMaterialsCogs | Credit Card: CreditCard | Equity: AccumulatedAdjustment, CommonStock, DividendDisbursed, OpeningBalanceEquity, OwnersEquity, PaidInCapitalOrSurplus, PartnerContributions, PartnerDistributions, PreferredStock, RetainedEarnings, TreasuryStock | Expense: AdvertisingPromotional, Auto, BadDebts, BankCharges, CharitableContributions, CommissionsAndFees, Communications, CostOfLabor, DuesSubscriptions, Entertainment, EntertainmentMeals, EquipmentRental, FinanceCosts, Insurance, InterestPaid, LegalProfessionalFees, OfficeGeneralAdministrativeExpenses, OtherBusinessExpenses, OtherMiscellaneousServiceCost, OtherSellingExpenses, PayrollExpenses, PayrollTaxExpenses, PayrollWageExpenses, PromotionalMeals, RentOrLeaseOfBuildings, RepairMaintenance, ShippingFreightDelivery, SuppliesMaterials, TaxesPaid, Travel, TravelMeals, UnappliedCashBillPaymentExpense, Utilities | Fixed Asset: AccumulatedAmortization, AccumulatedDepletion, AccumulatedDepreciation, Buildings, DepletableAssets, FixedAssetComputers, FixedAssetSoftware, FurnitureAndFixtures, IntangibleAssets, Land, LeaseholdImprovements, MachineryAndEquipment, OtherFixedAssets, Vehicles | Income: DiscountsRefundsGiven, NonProfitIncome, OtherPrimaryIncome, RevenueGeneral, SalesOfProductIncome, ServiceFeeIncome, UnappliedCashPaymentIncome | Long Term Liability: DebtsRelatedToParticipatingInterests, NotesPayable, OtherLongTermLiabilities, ShareholderNotesPayable | Other Asset: AccumulatedAmortizationOfOtherAssets, DeferredTax, Goodwill, IntangibleAssetsOther, LeaseBuyout, Licenses, LongTermInvestments, LongTermLoansAndAdvancesToRelatedParties, OrganizationalCosts, OtherLongTermAssets, SecurityDeposits | Other Current Asset: AllowanceForBadDebts, EmployeeCashAdvances, Inventory, Investment_MortgageRealEstateLoans, Investment_Other, Investment_TaxExemptSecurities, Investment_USGovernmentObligations, LoansToOfficers, LoansToOthers, LoansToStockholders, OtherCurrentAssets, PrepaidExpenses, Retainage, UndepositedFunds | Other Current Liability: DeferredRevenue, DirectDepositPayable, FederalIncomeTaxPayable, GlobalTaxPayable, LineOfCredit, LoanPayable, OtherCurrentLiabilities, PayrollClearing, PayrollTaxPayable, PrepaidExpensesPayable, SalesTaxPayable, StateLocalIncomeTaxPayable, TrustAccountsLiabilities | Other Expense: Amortization, Depreciation, ExchangeGainOrLoss, GasAndFuel, HomeOffice, OtherHomeOfficeExpenses, OtherMiscellaneousExpense, OtherVehicleExpenses, ParkingAndTolls, PenaltiesSettlements, VehicleInsurance, VehicleLoanInterest, VehicleRegistration, VehicleRepairs, WashAndRoadServices | Other Income: DividendIncome, GainLossOnSaleOfFixedAssets, GainLossOnSaleOfInvestments, InterestEarned, OtherInvestmentIncome, OtherMiscellaneousIncome, TaxExemptInterest
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_account",
"title": "Create Account",
"description": "Create a new account in the QuickBooks Online or Xero chart of accounts (COA). Use to add a general ledger account - expense, income, asset, liability, or equity account - when classifying transactions needs an account that does not yet exist. On Xero acct_num is REQUIRED and becomes the account Code that every Xero bill line addresses. A Xero BANK account cannot be created here: Xero requires the bank account number and NumbersGame does not handle bank account numbers, so tell the user to add it in Xero (Accounting > Chart of accounts > Add Bank Account); once it exists it is used here as normal. Xero has a single account type from its own vocabulary (EXPENSE, REVENUE, CURRENT, FIXED, and so on) rather than a type plus a sub_type, so sub_type is refused there rather than dropped. Xero's chart of accounts has no parent/child hierarchy, so there are no sub-accounts to create. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Account with \"created\": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_account applies it if you want it. It still refuses when the record holding the name is inactive, since an inactive record cannot be used on a document.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"type",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"minLength": 1
},
"type": {
"type": "string",
"minLength": 1,
"description": "On QuickBooks: AccountType, in spaced title case, one of: Accounts Payable, Accounts Receivable, Bank, Cost of Goods Sold, Credit Card, Equity, Expense, Fixed Asset, Income, Long Term Liability, Other Asset, Other Current Asset, Other Current Liability, Other Expense, Other Income. On Xero this is Xero's own single account type instead (EXPENSE, REVENUE, CURRENT, FIXED, ...), and sub_type must be omitted."
},
"acct_num": {
"type": "string",
"maxLength": 20,
"minLength": 1,
"description": "Account number/code. Optional on QuickBooks. REQUIRED for Xero companies, where every bill line refers to it."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"sub_type": {
"type": "string",
"description": "QuickBooks only; omit on Xero. AccountSubType, in spaceless PascalCase -- the casing differs from type, which is spaced. Supply it for an Equity account: omitting it makes QuickBooks default to OpeningBalanceEquity, of which a company may have only one, so the create fails with 'There can be only one account of detail type Opening Balance Equity'. Values seen in live companies, by type (examples, not an exhaustive list -- QuickBooks accepts others): Accounts Payable: AccountsPayable | Accounts Receivable: AccountsReceivable | Bank: CashOnHand, Checking, MoneyMarket, Savings, TrustAccounts | Cost of Goods Sold: CostOfLaborCos, EquipmentRentalCos, OtherCostsOfServiceCos, ShippingFreightDeliveryCos, SuppliesMaterialsCogs | Credit Card: CreditCard | Equity: AccumulatedAdjustment, CommonStock, DividendDisbursed, OpeningBalanceEquity, OwnersEquity, PaidInCapitalOrSurplus, PartnerContributions, PartnerDistributions, PreferredStock, RetainedEarnings, TreasuryStock | Expense: AdvertisingPromotional, Auto, BadDebts, BankCharges, CharitableContributions, CommissionsAndFees, Communications, CostOfLabor, DuesSubscriptions, Entertainment, EntertainmentMeals, EquipmentRental, FinanceCosts, Insurance, InterestPaid, LegalProfessionalFees, OfficeGeneralAdministrativeExpenses, OtherBusinessExpenses, OtherMiscellaneousServiceCost, OtherSellingExpenses, PayrollExpenses, PayrollTaxExpenses, PayrollWageExpenses, PromotionalMeals, RentOrLeaseOfBuildings, RepairMaintenance, ShippingFreightDelivery, SuppliesMaterials, TaxesPaid, Travel, TravelMeals, UnappliedCashBillPaymentExpense, Utilities | Fixed Asset: AccumulatedAmortization, AccumulatedDepletion, AccumulatedDepreciation, Buildings, DepletableAssets, FixedAssetComputers, FixedAssetSoftware, FurnitureAndFixtures, IntangibleAssets, Land, LeaseholdImprovements, MachineryAndEquipment, OtherFixedAssets, Vehicles | Income: DiscountsRefundsGiven, NonProfitIncome, OtherPrimaryIncome, RevenueGeneral, SalesOfProductIncome, ServiceFeeIncome, UnappliedCashPaymentIncome | Long Term Liability: DebtsRelatedToParticipatingInterests, NotesPayable, OtherLongTermLiabilities, ShareholderNotesPayable | Other Asset: AccumulatedAmortizationOfOtherAssets, DeferredTax, Goodwill, IntangibleAssetsOther, LeaseBuyout, Licenses, LongTermInvestments, LongTermLoansAndAdvancesToRelatedParties, OrganizationalCosts, OtherLongTermAssets, SecurityDeposits | Other Current Asset: AllowanceForBadDebts, EmployeeCashAdvances, Inventory, Investment_MortgageRealEstateLoans, Investment_Other, Investment_TaxExemptSecurities, Investment_USGovernmentObligations, LoansToOfficers, LoansToOthers, LoansToStockholders, OtherCurrentAssets, PrepaidExpenses, Retainage, UndepositedFunds | Other Current Liability: DeferredRevenue, DirectDepositPayable, FederalIncomeTaxPayable, GlobalTaxPayable, LineOfCredit, LoanPayable, OtherCurrentLiabilities, PayrollClearing, PayrollTaxPayable, PrepaidExpensesPayable, SalesTaxPayable, StateLocalIncomeTaxPayable, TrustAccountsLiabilities | Other Expense: Amortization, Depreciation, ExchangeGainOrLoss, GasAndFuel, HomeOffice, OtherHomeOfficeExpenses, OtherMiscellaneousExpense, OtherVehicleExpenses, ParkingAndTolls, PenaltiesSettlements, VehicleInsurance, VehicleLoanInterest, VehicleRegistration, VehicleRepairs, WashAndRoadServices | Other Income: DividendIncome, GainLossOnSaleOfFixedAssets, GainLossOnSaleOfInvestments, InterestEarned, OtherInvestmentIncome, OtherMiscellaneousIncome, TaxExemptInterest"
},
"description": {
"type": "string"
}
}
}
}
},
"annotations": {
"title": "Create Account",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Update an existing account in the QuickBooks Online or Xero chart of accounts (COA). On Xero there is no parent account and no sub-type, so those are refused by name; marking an account inactive archives it. Use to rename a general ledger account, change its description or parent account, or mark it inactive. Takes the account_id and a patch holding only the fields to change.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
3 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › account_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › patch
Fields to change, keyed by QuickBooks PascalCase property name: Name, Description, AccountType, AccountSubType, Active, SubAccount, ParentRef. ParentRef is a reference OBJECT, not an id — {"ParentRef": {"value": "49"}, "SubAccount": true} reparents an account. Do not send SyncToken or Id; both are fetched and supplied for you. Description is limited to 100 characters.
Clear enough to supply this argument.
params › clear_fields
Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_account",
"title": "Update Account",
"description": "Update an existing account in the QuickBooks Online or Xero chart of accounts (COA). On Xero there is no parent account and no sub-type, so those are refused by name; marking an account inactive archives it. Use to rename a general ledger account, change its description or parent account, or mark it inactive. Takes the account_id and a patch holding only the fields to change.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"account_id",
"patch",
"realm_id"
],
"properties": {
"patch": {
"type": "object",
"description": "Fields to change, keyed by QuickBooks PascalCase property name: Name, Description, AccountType, AccountSubType, Active, SubAccount, ParentRef. ParentRef is a reference OBJECT, not an id — {\"ParentRef\": {\"value\": \"49\"}, \"SubAccount\": true} reparents an account. Do not send SyncToken or Id; both are fetched and supplied for you. Description is limited to 100 characters.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"minLength": 1
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken."
}
}
}
}
},
"annotations": {
"title": "Update Account",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Search the chart of accounts (COA) in QuickBooks Online or Xero that match given criteria. Returns general ledger accounts - bank, credit card, expense, income, asset, liability, equity - with name, account type, classification, parent account and current balance. Filter by AccountType to pull one section of the ledger, or by Name to find a single account. This is also the standard way to confirm QuickBooks connectivity for a company, because unlike get_company_profile it is a real QBO read. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria
Filters. Either {filters:[{field,value,operator?}]} or a simple {Field: value} map. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused.On a QuickBooks company AccountType must be one of: Accounts Payable, Accounts Receivable, Bank, Cost of Goods Sold, Credit Card, Equity, Expense, Fixed Asset, Income, Long Term Liability, Other Asset, Other Current Asset, Other Current Liability, Other Expense, Other Income, and Classification one of: Asset, Equity, Expense, Liability, Revenue. On a Xero company the vocabulary is Xero's own (BANK, CURRENT, CURRLIAB, DIRECTCOSTS, EQUITY, EXPENSE, FIXED, INVENTORY, REVENUE, TERMLIAB and the rest); these QuickBooks names are translated where they map, and refused by name where Xero has no equivalent. Value types -- SubAccount and Active are booleans: send true or false, unquoted (the strings "true" and "false" are accepted too; nothing else is). CurrentBalance is a number: send it unquoted. MetaData.CreateTime and MetaData.LastUpdatedTime are dates: send strings, YYYY-MM-DD. Omit criteria entirely to return everything; an empty list [] means the same.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_accounts",
"title": "Search Accounts",
"description": "Search the chart of accounts (COA) in QuickBooks Online or Xero that match given criteria. Returns general ledger accounts - bank, credit card, expense, income, asset, liability, equity - with name, account type, classification, parent account and current balance. Filter by AccountType to pull one section of the ledger, or by Name to find a single account. This is also the standard way to confirm QuickBooks connectivity for a company, because unlike get_company_profile it is a real QBO read. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"criteria": {
"description": "Filters. Either {filters:[{field,value,operator?}]} or a simple {Field: value} map. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused.On a QuickBooks company AccountType must be one of: Accounts Payable, Accounts Receivable, Bank, Cost of Goods Sold, Credit Card, Equity, Expense, Fixed Asset, Income, Long Term Liability, Other Asset, Other Current Asset, Other Current Liability, Other Expense, Other Income, and Classification one of: Asset, Equity, Expense, Liability, Revenue. On a Xero company the vocabulary is Xero's own (BANK, CURRENT, CURRLIAB, DIRECTCOSTS, EQUITY, EXPENSE, FIXED, INVENTORY, REVENUE, TERMLIAB and the rest); these QuickBooks names are translated where they map, and refused by name where Xero has no equivalent. Value types -- SubAccount and Active are booleans: send true or false, unquoted (the strings \"true\" and \"false\" are accepted too; nothing else is). CurrentBalance is a number: send it unquoted. MetaData.CreateTime and MetaData.LastUpdatedTime are dates: send strings, YYYY-MM-DD. Omit criteria entirely to return everything; an empty list [] means the same."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Accounts",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Read a single item in QuickBooks Online or Xero by its ID. On Xero this reads Items/{id} and returns the Xero item, including its Code - the identity Xero invoice lines refer to, and what search_items exposes as Sku. Nothing else about this read differs between the two ledgers. For several items, use one search_items call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many read_item calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › item_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "read_item",
"title": "Get Item",
"description": "Read a single item in QuickBooks Online or Xero by its ID. On Xero this reads Items/{id} and returns the Xero item, including its Code - the identity Xero invoice lines refer to, and what search_items exposes as Sku. Nothing else about this read differs between the two ledgers. For several items, use one search_items call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many read_item calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"item_id",
"realm_id"
],
"properties": {
"item_id": {
"type": "string",
"minLength": 1
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Item",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Search items in QuickBooks Online or Xero using criteria (maps to node-quickbooks findItems on QuickBooks). On Xero this reads the Items endpoint and Sku maps to Code, which is the identity every Xero invoice line refers to. Xero items have no active flag - they are deleted rather than archived - and no item type, so Active and Type are refused by name rather than silently dropped, as are FullyQualifiedName, ParentRef and MetaData.CreateTime. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria
Filters. Either {filters:[{field,value,operator?}]} or a simple {Field: value} map. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused.Type must be one of: Inventory, Service, NonInventory, Category, Group. Type is QuickBooks only - Xero has no item type and refuses the filter rather than dropping it. Value types -- Active is a boolean: send true or false, unquoted (the strings "true" and "false" are accepted too; nothing else is). UnitPrice and QtyOnHand are numbers: send them unquoted. MetaData.CreateTime and MetaData.LastUpdatedTime are dates: send strings, YYYY-MM-DD. Omit criteria entirely to return everything; an empty list [] means the same.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_items",
"title": "Search Items",
"description": "Search items in QuickBooks Online or Xero using criteria (maps to node-quickbooks findItems on QuickBooks). On Xero this reads the Items endpoint and Sku maps to Code, which is the identity every Xero invoice line refers to. Xero items have no active flag - they are deleted rather than archived - and no item type, so Active and Type are refused by name rather than silently dropped, as are FullyQualifiedName, ParentRef and MetaData.CreateTime. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"criteria": {
"description": "Filters. Either {filters:[{field,value,operator?}]} or a simple {Field: value} map. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused.Type must be one of: Inventory, Service, NonInventory, Category, Group. Type is QuickBooks only - Xero has no item type and refuses the filter rather than dropping it. Value types -- Active is a boolean: send true or false, unquoted (the strings \"true\" and \"false\" are accepted too; nothing else is). UnitPrice and QtyOnHand are numbers: send them unquoted. MetaData.CreateTime and MetaData.LastUpdatedTime are dates: send strings, YYYY-MM-DD. Omit criteria entirely to return everything; an empty list [] means the same."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Items",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Create a product or service item in QuickBooks Online or Xero. On Xero an item code (sku) is REQUIRED - Xero uses it as the item identity on every invoice and bill line - and only Service or NonInventory types are accepted, because tracked inventory needs an inventory asset account and a cost-of-goods-sold account this tool has no fields for. Xero items have no active flag, so remove one with delete_item rather than deactivating it. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Item with "created": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_item applies it if you want it. It still refuses when the record holding the name is inactive, since an inactive record cannot be used on a document.
The description explains the capability, when to use it, and what to expect.
Inputs22/100
2 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sku
Item code/SKU. Optional on QuickBooks. REQUIRED for Xero companies, where it is the code every invoice line refers to.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › type
Not provided
Missing description. Explain what this value means and how to supply it.
params › income_account_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › expense_account_ref
Not provided
Missing description. Explain what this value means and how to supply it.
params › unit_price
Not provided
Missing description. Explain what this value means and how to supply it.
params › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_item",
"title": "Create Item",
"description": "Create a product or service item in QuickBooks Online or Xero. On Xero an item code (sku) is REQUIRED - Xero uses it as the item identity on every invoice and bill line - and only Service or NonInventory types are accepted, because tracked inventory needs an inventory asset account and a cost-of-goods-sold account this tool has no fields for. Xero items have no active flag, so remove one with delete_item rather than deactivating it. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Item with \"created\": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_item applies it if you want it. It still refuses when the record holding the name is inactive, since an inactive record cannot be used on a document.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"type",
"income_account_ref",
"realm_id"
],
"properties": {
"sku": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Item code/SKU. Optional on QuickBooks. REQUIRED for Xero companies, where it is the code every invoice line refers to."
},
"name": {
"type": "string",
"minLength": 1
},
"type": {
"type": "string",
"minLength": 1
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"unit_price": {
"type": "number"
},
"description": {
"type": "string"
},
"income_account_ref": {
"type": "string",
"minLength": 1
},
"expense_account_ref": {
"type": "string"
}
}
}
}
},
"annotations": {
"title": "Create Item",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Update an existing item in QuickBooks Online or Xero by ID (sparse update). On Xero the sku is the item Code, sales and purchase details are merged rather than replaced, and there is no active flag - use delete_item to remove an item. clear_fields is not supported on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
2 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › item_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › patch
Not provided
Missing description. Explain what this value means and how to supply it.
params › clear_fields
Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_item",
"title": "Update Item",
"description": "Update an existing item in QuickBooks Online or Xero by ID (sparse update). On Xero the sku is the item Code, sales and purchase details are merged rather than replaced, and there is no active flag - use delete_item to remove an item. clear_fields is not supported on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"item_id",
"patch",
"realm_id"
],
"properties": {
"patch": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"item_id": {
"type": "string",
"minLength": 1
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to EMPTY. Omitting a field from patch never empties it - ordinary updates are sparse, so an omitted value is left alone. This costs a full rewrite of the record, so use it only to genuinely empty a value; to CHANGE one, put it in patch. Cannot clear Id or SyncToken."
}
}
}
}
},
"annotations": {
"title": "Update Item",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Delete a product or service item in Xero. Xero items have no active or archived status, so deleting is the only way to remove one - which is also why search_items refuses an Active filter. Xero refuses the delete if the item has been used on an invoice or bill, and says so. This tool is Xero only: QuickBooks Online does not delete items, it deactivates them, so on a QuickBooks company use update_item with a patch of Active false instead.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Resolve the mismatch between this description and its schema constraints.
params › item_id
The Xero ItemID (a GUID). Get it from search_items or read_item.
Resolve the mismatch between this description and its schema constraints.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_item",
"title": "Delete Item",
"description": "Delete a product or service item in Xero. Xero items have no active or archived status, so deleting is the only way to remove one - which is also why search_items refuses an Active filter. Xero refuses the delete if the item has been used on an invoice or bill, and says so. This tool is Xero only: QuickBooks Online does not delete items, it deactivates them, so on a QuickBooks company use update_item with a patch of Active false instead.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"item_id",
"realm_id"
],
"properties": {
"item_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The Xero ItemID (a GUID). Get it from search_items or read_item."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Delete Item",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Create a vendor in QuickBooks Online, or a contact in Xero. On Xero this creates a Contact identical to the one create_customer creates: Xero keeps ONE contact record for both roles and marks it a supplier only once a bill is posted against it. Xero has a single Name field, so DisplayName and CompanyName cannot both be kept - sending two different values is refused rather than losing one. Vendor1099, AcctNum, PrintOnCheckName, TermRef and CurrencyRef have no Xero home and are refused by name rather than dropped: Xero has no 1099 flag on a contact (1099 status comes from the 1099 rules in Xero, read with report_1099). TaxIdentifier is never passed on, on QuickBooks or Xero, because NumbersGame does not handle social security, tax id or bank account numbers: a tax id typed into a chat is dropped and the reply says so. Set Vendor1099 here and enter the TIN in the ledger from the vendor's W-9; get_vendor then shows its type and last 4. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Vendor with "created": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_vendor applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).
The description explains the capability, when to use it, and what to expect.
Inputs15/100
2 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › vendor › DisplayName
Vendor display name (required, must be unique across the shared name list). QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › vendor › GivenName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › FamilyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › CompanyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › Line1
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › City
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › Country
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › PostalCode
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_vendor",
"title": "Create Vendor",
"description": "Create a vendor in QuickBooks Online, or a contact in Xero. On Xero this creates a Contact identical to the one create_customer creates: Xero keeps ONE contact record for both roles and marks it a supplier only once a bill is posted against it. Xero has a single Name field, so DisplayName and CompanyName cannot both be kept - sending two different values is refused rather than losing one. Vendor1099, AcctNum, PrintOnCheckName, TermRef and CurrencyRef have no Xero home and are refused by name rather than dropped: Xero has no 1099 flag on a contact (1099 status comes from the 1099 rules in Xero, read with report_1099). TaxIdentifier is never passed on, on QuickBooks or Xero, because NumbersGame does not handle social security, tax id or bank account numbers: a tax id typed into a chat is dropped and the reply says so. Set Vendor1099 here and enter the TIN in the ledger from the vendor's W-9; get_vendor then shows its type and last 4. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Vendor with \"created\": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_vendor applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor",
"realm_id"
],
"properties": {
"vendor": {
"type": "object",
"required": [
"DisplayName"
],
"properties": {
"BillAddr": {
"type": "object",
"properties": {
"City": {
"type": "string"
},
"Line1": {
"type": "string"
},
"Country": {
"type": "string"
},
"PostalCode": {
"type": "string"
},
"CountrySubDivisionCode": {
"type": "string"
}
},
"additionalProperties": {}
},
"GivenName": {
"type": "string"
},
"FamilyName": {
"type": "string"
},
"CompanyName": {
"type": "string"
},
"DisplayName": {
"type": "string",
"description": "Vendor display name (required, must be unique across the shared name list). QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"properties": {
"FreeFormNumber": {
"type": "string"
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"properties": {
"Address": {
"type": "string"
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Vendor",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Update a vendor in QuickBooks Online or Xero. TaxIdentifier is never passed on, because NumbersGame does not handle social security, tax id or bank account numbers: a tax id typed into a chat is dropped and the reply says so (the TIN already on file is kept); enter it in the ledger from the vendor's W-9. Xero holds one contact record for customers and suppliers, so this edits the same record update_customer does; 1099 status and payment terms have no Xero equivalent and are refused by name (1099 status comes from the 1099 rules in Xero, read with report_1099). A tax identifier is refused on Xero too, because this tool does not write Xero's tax number yet: set it on the contact in Xero (get_vendor reads it back as TaxNumber). Archiving a Xero contact that still has money owed on either side needs confirm_archive: true, and Xero's API cannot restore an archived contact. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).
The description explains the capability, when to use it, and what to expect.
Inputs27/100
4 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › vendor › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › SyncToken
QuickBooks optimistic-concurrency token, from the record you are updating. REQUIRED for QuickBooks companies. Xero has no equivalent and refuses it — omit it there; concurrent Xero updates are last-writer-wins.
Clear enough to supply this argument.
params › vendor › DisplayName
REQUIRED for QuickBooks companies, which reject a vendor update without it. Optional for Xero, where resending a name you did not mean to change can RENAME the contact as a side effect of editing an email address. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Clear enough to supply this argument.
params › vendor › GivenName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › FamilyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › CompanyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › Line1
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › City
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › Country
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › vendor › BillAddr › PostalCode
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_archive
Xero only; ignored on QuickBooks. Archiving a Xero contact (Active: false, or ContactStatus ARCHIVED) that still has money owed on either side -- unpaid invoices or unpaid bills -- needs confirm_archive: true, on the first call, once the user has agreed. Xero keeps one record for customer and supplier, so the archive covers both, and Xero's API cannot restore an archived contact: only a person in Xero can.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_vendor",
"title": "Update Vendor",
"description": "Update a vendor in QuickBooks Online or Xero. TaxIdentifier is never passed on, because NumbersGame does not handle social security, tax id or bank account numbers: a tax id typed into a chat is dropped and the reply says so (the TIN already on file is kept); enter it in the ledger from the vendor's W-9. Xero holds one contact record for customers and suppliers, so this edits the same record update_customer does; 1099 status and payment terms have no Xero equivalent and are refused by name (1099 status comes from the 1099 rules in Xero, read with report_1099). A tax identifier is refused on Xero too, because this tool does not write Xero's tax number yet: set it on the contact in Xero (get_vendor reads it back as TaxNumber). Archiving a Xero contact that still has money owed on either side needs confirm_archive: true, and Xero's API cannot restore an archived contact. An email set or changed here (PrimaryEmailAddr) is held at its first send until a person confirms it in NumbersGame (Firm settings → Document sending → Recipients).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor",
"realm_id"
],
"properties": {
"vendor": {
"type": "object",
"required": [
"Id"
],
"properties": {
"Id": {
"type": "string"
},
"BillAddr": {
"type": "object",
"properties": {
"City": {
"type": "string"
},
"Line1": {
"type": "string"
},
"Country": {
"type": "string"
},
"PostalCode": {
"type": "string"
},
"CountrySubDivisionCode": {
"type": "string"
}
},
"additionalProperties": {}
},
"GivenName": {
"type": "string"
},
"SyncToken": {
"type": "string",
"description": "QuickBooks optimistic-concurrency token, from the record you are updating. REQUIRED for QuickBooks companies. Xero has no equivalent and refuses it — omit it there; concurrent Xero updates are last-writer-wins."
},
"FamilyName": {
"type": "string"
},
"CompanyName": {
"type": "string"
},
"DisplayName": {
"type": "string",
"description": "REQUIRED for QuickBooks companies, which reject a vendor update without it. Optional for Xero, where resending a name you did not mean to change can RENAME the contact as a side effect of editing an email address. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"properties": {
"FreeFormNumber": {
"type": "string"
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"properties": {
"Address": {
"type": "string"
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"confirm_archive": {
"type": "boolean",
"description": "Xero only; ignored on QuickBooks. Archiving a Xero contact (Active: false, or ContactStatus ARCHIVED) that still has money owed on either side -- unpaid invoices or unpaid bills -- needs confirm_archive: true, on the first call, once the user has agreed. Xero keeps one record for customer and supplier, so the archive covers both, and Xero's API cannot restore an archived contact: only a person in Xero can."
}
}
}
}
},
"annotations": {
"title": "Update Vendor",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Get a vendor by ID from QuickBooks Online or Xero. On Xero this reads Contacts/{id} - the SAME record get_customer reads, because Xero keeps one contact record for both roles and derives supplier status from the bills posted against it rather than from a flag on the record. On Xero a vendor's tax id is the contact's TaxNumber, with TaxNumberType (SSN, EIN, ITIN or ATIN), masked to its last 4 digits (NumbersGame never returns a full tax id; Xero itself masks it for roles other than Adviser). Xero has no 1099 flag on a contact; report_1099 reads which vendors are on Xero's 1099 report. For several vendors, use one search_vendors call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_vendor calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_vendor",
"title": "Get Vendor",
"description": "Get a vendor by ID from QuickBooks Online or Xero. On Xero this reads Contacts/{id} - the SAME record get_customer reads, because Xero keeps one contact record for both roles and derives supplier status from the bills posted against it rather than from a flag on the record. On Xero a vendor's tax id is the contact's TaxNumber, with TaxNumberType (SSN, EIN, ITIN or ATIN), masked to its last 4 digits (NumbersGame never returns a full tax id; Xero itself masks it for roles other than Adviser). Xero has no 1099 flag on a contact; report_1099 reads which vendors are on Xero's 1099 report. For several vendors, use one search_vendors call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_vendor calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Vendor",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Search vendors in QuickBooks Online, or supplier contacts in Xero, that match given criteria. On Xero this reads the Contacts endpoint - the SAME records search_customers reads, because Xero keeps one contact record for both roles and derives supplier status from the bills posted against a contact rather than from a flag. There is no supplier field to filter on, so on Xero this returns contacts, not vendors specifically. DisplayName and CompanyName both map to Xero's single Name field. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. Balance, MiddleName, PrintOnCheckName, BillRate and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped. On Xero a vendor's tax id is the contact's TaxNumber, with TaxNumberType (SSN, EIN, ITIN or ATIN), masked to its last 4 digits (NumbersGame never returns a full tax id; Xero itself masks it for roles other than Adviser). Xero has no 1099 flag on a contact; report_1099 reads which vendors are on Xero's 1099 report. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Vendor entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, GivenName, MiddleName, FamilyName, CompanyName, DisplayName, PrintOnCheckName, Active, Balance, BillRate. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Vendor entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, GivenName, MiddleName, FamilyName, CompanyName, DisplayName, PrintOnCheckName, Active, Balance, BillRate. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_vendors",
"title": "Search Vendors",
"description": "Search vendors in QuickBooks Online, or supplier contacts in Xero, that match given criteria. On Xero this reads the Contacts endpoint - the SAME records search_customers reads, because Xero keeps one contact record for both roles and derives supplier status from the bills posted against a contact rather than from a flag. There is no supplier field to filter on, so on Xero this returns contacts, not vendors specifically. DisplayName and CompanyName both map to Xero's single Name field. Xero's filter language has no IN and no wildcards, so IN is refused (query one value at a time) and LIKE becomes a Contains match. Balance, MiddleName, PrintOnCheckName, BillRate and MetaData.CreateTime have no Xero equivalent and are refused by name rather than silently dropped. On Xero a vendor's tax id is the contact's TaxNumber, with TaxNumberType (SSN, EIN, ITIN or ATIN), masked to its last 4 digits (NumbersGame never returns a full tax id; Xero itself masks it for roles other than Adviser). Xero has no 1099 flag on a contact; report_1099 reads which vendors are on Xero's 1099 report. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"enum": [
"Id",
"DisplayName",
"CompanyName",
"Balance",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime"
],
"type": "string"
},
"desc": {
"enum": [
"Id",
"DisplayName",
"CompanyName",
"Balance",
"MetaData.CreateTime",
"MetaData.LastUpdatedTime"
],
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Vendor entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, GivenName, MiddleName, FamilyName, CompanyName, DisplayName, PrintOnCheckName, Active, Balance, BillRate. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
},
"additionalProperties": false
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Vendor entity. One of: Id, MetaData.CreateTime, MetaData.LastUpdatedTime, GivenName, MiddleName, FamilyName, CompanyName, DisplayName, PrintOnCheckName, Active, Balance, BillRate. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
},
"additionalProperties": false
}
]
},
"maxItems": 20,
"description": "Filters to apply. Unknown fields are rejected instead of silently broadening the query. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Search Vendors",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Create an employee in QuickBooks Online. Not available for Xero companies: this connector reads Xero UK Payroll (search_employees, get_employee) but does not write it; make the change in Xero Payroll. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Employee with "created": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_employee applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive.
The description explains the capability, when to use it, and what to expect.
Inputs46/100
4 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › employee › GivenName
Employee first name (required)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › employee › FamilyName
Employee last name (required)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › employee › DisplayName
Employee display name. QuickBooks builds it from GivenName and FamilyName when omitted. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › employee › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › BillAddr
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_employee",
"title": "Create Employee",
"description": "Create an employee in QuickBooks Online. Not available for Xero companies: this connector reads Xero UK Payroll (search_employees, get_employee) but does not write it; make the change in Xero Payroll. IF THE NAME IS ALREADY TAKEN this does not fail: it returns the existing Employee with \"created\": false and changes nothing, so you can use its Id straight away. Any field you sent that differs from that record is listed and NOT applied -- update_employee applies it if you want it. Two cases still refuse, because there is no record to hand back: the name belongs to a customer, vendor or employee of a DIFFERENT type (QuickBooks keeps all three in one name list, and the refusal names the type), or the record holding it is inactive.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"employee",
"realm_id"
],
"properties": {
"employee": {
"type": "object",
"required": [
"GivenName",
"FamilyName"
],
"properties": {
"BillAddr": {},
"GivenName": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Employee first name (required)"
},
"FamilyName": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Employee last name (required)"
},
"DisplayName": {
"type": "string",
"maxLength": 500,
"description": "Employee display name. QuickBooks builds it from GivenName and FamilyName when omitted. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"required": [
"FreeFormNumber"
],
"properties": {
"FreeFormNumber": {
"type": "string"
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"required": [
"Address"
],
"properties": {
"Address": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Employee",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description55/100
Get an employee by Id from QuickBooks Online. On a Xero company the Id is a Xero UK Payroll employeeID (from search_employees) and this returns that payroll employee with start and end date, employee number and saved department. Xero UK Payroll only, approved by a Payroll Administrator. For several employees, use one search_employees call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_employee calls in parallel, which QuickBooks rate-limits (code 3001).
Resolve contradictions between the description, input schema, and annotations.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_employee",
"title": "Get Employee",
"description": "Get an employee by Id from QuickBooks Online. On a Xero company the Id is a Xero UK Payroll employeeID (from search_employees) and this returns that payroll employee with start and end date, employee number and saved department. Xero UK Payroll only, approved by a Payroll Administrator. For several employees, use one search_employees call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_employee calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Employee",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description73/100
Update an employee in QuickBooks Online. Not available for Xero companies: this connector reads Xero UK Payroll (search_employees, get_employee) but does not write it; make the change in Xero Payroll.
The description explains the capability, when to use it, and what to expect.
Inputs31/100
4 of 9 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › employee › Id
QBO Employee ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › employee › SyncToken
Optimistic concurrency token
Explain the meaning of this value, not just its name.
params › employee › DisplayName
Employee display name; must stay unique across the shared name list. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \ | " and accented letters, is accepted, so do not strip punctuation). A name like "3:16 Cafe" must be sent as "3-16 Cafe". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › employee › GivenName
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › FamilyName
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › Active
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › PrimaryPhone › FreeFormNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › employee › PrimaryEmailAddr › Address
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_employee",
"title": "Update Employee",
"description": "Update an employee in QuickBooks Online. Not available for Xero companies: this connector reads Xero UK Payroll (search_employees, get_employee) but does not write it; make the change in Xero Payroll.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"employee",
"realm_id"
],
"properties": {
"employee": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Employee ID"
},
"Active": {
"type": "boolean"
},
"GivenName": {
"type": "string",
"maxLength": 100
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token"
},
"FamilyName": {
"type": "string",
"maxLength": 100
},
"DisplayName": {
"type": "string",
"maxLength": 500,
"description": "Employee display name; must stay unique across the shared name list. QuickBooks refuses exactly three characters in this name — a COLON, a tab and a newline (measured 2026-09-17; every other symbol, including & \\ | \" and accented letters, is accepted, so do not strip punctuation). A name like \"3:16 Cafe\" must be sent as \"3-16 Cafe\". Nothing is lost by this: the restriction is the shared name list's alone, so put the name exactly as the client writes it in CompanyName (and PrintOnCheckName on a vendor paid by cheque), which both accept the colon. On an employee QuickBooks builds this name from GivenName and FamilyName, so keep those clear of it too. Say which name you changed and to what, because the bookkeeper will search for the original."
},
"PrimaryPhone": {
"type": "object",
"required": [
"FreeFormNumber"
],
"properties": {
"FreeFormNumber": {
"type": "string",
"maxLength": 30
}
}
},
"PrimaryEmailAddr": {
"type": "object",
"required": [
"Address"
],
"properties": {
"Address": {
"type": "string",
"maxLength": 100
}
}
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Update Employee",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Search employees in QuickBooks Online that match given criteria. On a Xero company this searches Xero UK Payroll instead, applying the Id, DisplayName, GivenName, FamilyName and Active filters (Active = on payroll today); the other fields are not held there, and the result names any it could not apply. Each match carries its start and end date, whether it is on payroll today, and the department saved with set_employee_departments, plus which matches on payroll have no department yet. Xero answers only for an organisation running Xero UK Payroll whose connection was approved by a Payroll Administrator; otherwise the refusal says which and how to fix it. For headcount over time and employer cost use report_payroll_costs. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Employee entity. One of: Id, DisplayName, GivenName, FamilyName, Active, PrimaryEmailAddr, PrintOnCheckName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Employee entity. One of: Id, DisplayName, GivenName, FamilyName, Active, PrimaryEmailAddr, PrintOnCheckName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_employees",
"title": "Search Employees",
"description": "Search employees in QuickBooks Online that match given criteria. On a Xero company this searches Xero UK Payroll instead, applying the Id, DisplayName, GivenName, FamilyName and Active filters (Active = on payroll today); the other fields are not held there, and the result names any it could not apply. Each match carries its start and end date, whether it is on payroll today, and the department saved with set_employee_departments, plus which matches on payroll have no department yet. Xero answers only for an organisation running Xero UK Payroll whose connection was approved by a Payroll Administrator; otherwise the refusal says which and how to fix it. For headcount over time and employer cost use report_payroll_costs. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Employee entity. One of: Id, DisplayName, GivenName, FamilyName, Active, PrimaryEmailAddr, PrintOnCheckName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Employee entity. One of: Id, DisplayName, GivenName, FamilyName, Active, PrimaryEmailAddr, PrintOnCheckName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Employees",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Create a class (profit center / project) in QuickBooks Online. Use classes to categorize transactions by project, property, or business segment. Always search_classes first to avoid duplicates.On Xero a class is an OPTION inside a tracking category, not a category itself - mapping it to the category level would create a new reporting dimension every time somebody added a class. This adds the option to the category named Class, or to the organisation's only category if it has one. It will NOT create a category: Xero allows only two, one can never be deleted, and an unused one cannot even be archived, so that choice belongs in Xero where its cost is visible. Naming an existing class is not an error - it returns the one already there rather than a duplicate.
The description explains the capability, when to use it, and what to expect.
Inputs73/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class › Name
Class name (required)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class › SubClass
Set true if this is a sub-class
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class › ParentRef › value
Parent class ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › class › ParentRef › name
Parent class name
Explain the meaning of this value, not just its name.
params › class › Active
Active status (default true)
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_class",
"title": "Create Class",
"description": "Create a class (profit center / project) in QuickBooks Online. Use classes to categorize transactions by project, property, or business segment. Always search_classes first to avoid duplicates.On Xero a class is an OPTION inside a tracking category, not a category itself - mapping it to the category level would create a new reporting dimension every time somebody added a class. This adds the option to the category named Class, or to the organisation's only category if it has one. It will NOT create a category: Xero allows only two, one can never be deleted, and an unused one cannot even be archived, so that choice belongs in Xero where its cost is visible. Naming an existing class is not an error - it returns the one already there rather than a duplicate.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"class",
"realm_id"
],
"properties": {
"class": {
"type": "object",
"required": [
"Name"
],
"properties": {
"Name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Class name (required)"
},
"Active": {
"type": "boolean",
"description": "Active status (default true)"
},
"SubClass": {
"type": "boolean",
"description": "Set true if this is a sub-class"
},
"ParentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"description": "Parent class name"
},
"value": {
"type": "string",
"description": "Parent class ID"
}
},
"description": "Parent class ref for sub-classes"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Class",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Get a class by Id from QuickBooks Online.On Xero this reads a tracking option by id or name, and reports which tracking category it belongs to - two categories can hold options with the same name. For several classes, use one search_classes call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_class calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › id
The ID of the class to retrieve
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_class",
"title": "Get Class",
"description": "Get a class by Id from QuickBooks Online.On Xero this reads a tracking option by id or name, and reports which tracking category it belongs to - two categories can hold options with the same name. For several classes, use one search_classes call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_class calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The ID of the class to retrieve"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Class",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Update a class in QuickBooks Online. To deactivate a class, set Active to false. Requires Id and SyncToken from a prior get_class call.On Xero this renames a tracking option, or archives it when Active is false. Xero has no delete for these.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
7 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › class › Id
Class ID (required for update)
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › class › SyncToken
Sync token (required — get from get_class)
Clear enough to supply this argument.
params › class › Name
Updated class name
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class › SubClass
Set true if this is a sub-class
Explain the meaning of this value, not just its name.
params › class › ParentRef › value
Parent class ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › class › ParentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › class › Active
Set false to deactivate
Explain what happens when this optional value is omitted.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_class",
"title": "Update Class",
"description": "Update a class in QuickBooks Online. To deactivate a class, set Active to false. Requires Id and SyncToken from a prior get_class call.On Xero this renames a tracking option, or archives it when Active is false. Xero has no delete for these.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"class",
"realm_id"
],
"properties": {
"class": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"description": "Class ID (required for update)"
},
"Name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Updated class name"
},
"Active": {
"type": "boolean",
"description": "Set false to deactivate"
},
"SubClass": {
"type": "boolean",
"description": "Set true if this is a sub-class"
},
"ParentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"description": "Parent class ID"
}
},
"description": "Parent class ref for sub-classes"
},
"SyncToken": {
"type": "string",
"description": "Sync token (required — get from get_class)"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Update Class",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Search classes in QuickBooks Online. Use this to find existing classes before creating transactions with ClassRef, or before creating new classes to avoid duplicates.On Xero this lists the tracking options across every active category, each reporting the category it belongs to. A QuickBooks class is an option, not a category. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
4 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › field
Field to filter on - a property of the QuickBooks Online Class entity. One of: Id, Name, Active, FullyQualifiedName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_classes",
"title": "Search Classes",
"description": "Search classes in QuickBooks Online. Use this to find existing classes before creating transactions with ClassRef, or before creating new classes to avoid duplicates.On Xero this lists the tracking options across every active category, each reporting the category it belongs to. A QuickBooks class is an option, not a category. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Class entity. One of: Id, Name, Active, FullyQualifiedName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
"description": "Filters to apply. Use {field, value, operator?} triples. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Classes",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description77/100
Create a department (cost center / location) in QuickBooks Online. Use departments to categorize transactions by business unit, location, or team. Always search_departments first to avoid duplicates.On Xero this is REFUSED, and deliberately: Xero allows only TWO active tracking categories in the whole organisation, so mapping both class and department would spend a firm's entire tracking budget - and a category can never be deleted once created. Class takes the slot because it is the more common QuickBooks usage. To track a second dimension, create the category in Xero and use the class tools against it.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › department › Name
Department name (required)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › department › SubDepartment
Set true if this is a sub-department
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › department › ParentRef › value
Parent department ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › department › ParentRef › name
Parent department name
Explain the meaning of this value, not just its name.
params › department › Active
Active status (default true)
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_department",
"title": "Create Department",
"description": "Create a department (cost center / location) in QuickBooks Online. Use departments to categorize transactions by business unit, location, or team. Always search_departments first to avoid duplicates.On Xero this is REFUSED, and deliberately: Xero allows only TWO active tracking categories in the whole organisation, so mapping both class and department would spend a firm's entire tracking budget - and a category can never be deleted once created. Class takes the slot because it is the more common QuickBooks usage. To track a second dimension, create the category in Xero and use the class tools against it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"department",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"department": {
"type": "object",
"required": [
"Name"
],
"properties": {
"Name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Department name (required)"
},
"Active": {
"type": "boolean",
"description": "Active status (default true)"
},
"ParentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"description": "Parent department name"
},
"value": {
"type": "string",
"description": "Parent department ID"
}
},
"description": "Parent department ref for sub-departments"
},
"SubDepartment": {
"type": "boolean",
"description": "Set true if this is a sub-department"
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Department",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Get a department by Id from QuickBooks Online.On Xero this is REFUSED: Xero has no departments, and its tracking categories are limited to two - see create_department for why class takes the slot. For several departments, use one search_departments call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_department calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › id
The ID of the department to retrieve
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_department",
"title": "Get Department",
"description": "Get a department by Id from QuickBooks Online.On Xero this is REFUSED: Xero has no departments, and its tracking categories are limited to two - see create_department for why class takes the slot. For several departments, use one search_departments call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_department calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The ID of the department to retrieve"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Department",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Update a department in QuickBooks Online. To deactivate, set Active to false. Requires Id and SyncToken from a prior get_department call.On Xero this is REFUSED: Xero has no departments - see create_department.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
7 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › department › Id
Department ID (required for update)
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › department › SyncToken
Sync token (required — get from get_department)
Clear enough to supply this argument.
params › department › Name
Updated department name
Clear enough to supply this argument.
params › department › SubDepartment
Set true if this is a sub-department
Explain what happens when this optional value is omitted.
params › department › ParentRef › value
Parent department ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › department › ParentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › department › Active
Set false to deactivate
Explain what happens when this optional value is omitted.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_department",
"title": "Update Department",
"description": "Update a department in QuickBooks Online. To deactivate, set Active to false. Requires Id and SyncToken from a prior get_department call.On Xero this is REFUSED: Xero has no departments - see create_department.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"department",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"department": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"description": "Department ID (required for update)"
},
"Name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Updated department name"
},
"Active": {
"type": "boolean",
"description": "Set false to deactivate"
},
"ParentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"description": "Parent department ID"
}
},
"description": "Parent department ref for sub-departments"
},
"SyncToken": {
"type": "string",
"description": "Sync token (required — get from get_department)"
},
"SubDepartment": {
"type": "boolean",
"description": "Set true if this is a sub-department"
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Update Department",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Search departments in QuickBooks Online. Use this to find existing departments before creating transactions with DepartmentRef, or before creating new departments to avoid duplicates.On Xero this is REFUSED: Xero has no departments. Its equivalent is a tracking category, limited to two, and class takes the slot - see create_department. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it "... (deleted)" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.
The description explains the capability, when to use it, and what to expect.
Inputs38/100
4 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › field
Field to filter on - a property of the QuickBooks Online Department entity. One of: Id, Name, Active, FullyQualifiedName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Clear enough to supply this argument.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_departments",
"title": "Search Departments",
"description": "Search departments in QuickBooks Online. Use this to find existing departments before creating transactions with DepartmentRef, or before creating new departments to avoid duplicates.On Xero this is REFUSED: Xero has no departments. Its equivalent is a tracking category, limited to two, and class takes the slot - see create_department. In QuickBooks Online a search with no Active filter returns only ACTIVE records: deactivating a record renames it \"... (deleted)\" and hides it from every query, so a search that should have matched it comes back empty as though the record never existed - pass Active = false in the criteria to find one that has been deactivated.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Department entity. One of: Id, Name, Active, FullyQualifiedName, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
"description": "Filters to apply. Use {field, value, operator?} triples. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Departments",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Search transactions that could receive a Class or Department assignment, and return them for human review. Read-only — applies nothing. Filters by date range or bank account. Max 100 per batch. After approval, pass the results to bulk_assign_classification to apply them. On Xero a class is a tracking-category option and there are no departments; a date_range preview also lists supplier bills (not voided or deleted), which have no bank account and so are left out of an account preview. Bank transfers cannot be classified after they are created, and are reported individually rather than counted as failures.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › filter_type
How to filter transactions
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Start date (YYYY-MM-DD) for date_range filter
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
End date (YYYY-MM-DD) for date_range filter
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › account_id
Bank account ID for account filter
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "preview_bulk_classification",
"title": "Preview Bulk Classification",
"description": "Search transactions that could receive a Class or Department assignment, and return them for human review. Read-only — applies nothing. Filters by date range or bank account. Max 100 per batch. After approval, pass the results to bulk_assign_classification to apply them. On Xero a class is a tracking-category option and there are no departments; a date_range preview also lists supplier bills (not voided or deleted), which have no bank account and so are left out of an account preview. Bank transfers cannot be classified after they are created, and are reported individually rather than counted as failures.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"filter_type",
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "End date (YYYY-MM-DD) for date_range filter"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Bank account ID for account filter"
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date (YYYY-MM-DD) for date_range filter"
},
"filter_type": {
"enum": [
"date_range",
"account"
],
"type": "string",
"description": "How to filter transactions"
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Preview Bulk Classification",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Apply a Class or Department assignment to transactions already approved by a human. Writes to QuickBooks. Get the transaction list from preview_bulk_classification first — this tool only applies what you pass it. Max 100 per batch. On QuickBooks the class is written onto each line of a purchase, deposit or journal entry, and every record is checked after saving: a QuickBooks Transfer has no lines, and on a company that tracks class per line QuickBooks accepts the class and discards it, so such a transfer is reported as a failure naming that, never as updated. On Xero a class is a tracking-category option (pass its id or name) and there are no departments; bills, spend and receive money and manual journals can be classified, every line gets the option, and a line's tag in the organisation's OTHER tracking category is kept. A paid bill stays paid. Bank transfers cannot be classified after they are created, and a reconciled bank transaction is locked by Xero; both are reported individually rather than counted as failures.
Describe the returned information so the agent knows whether it will answer the request.
Inputs72/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class_ref › value
QBO entity ID
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class_ref › name
Display name
Explain the meaning of this value, not just its name.
params › department_ref › value
QBO entity ID
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › department_ref › name
Display name
Explain the meaning of this value, not just its name.
SyncToken from preview results. Empty string for Xero, which has none.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "bulk_assign_classification",
"title": "Bulk Assign Classification",
"description": "Apply a Class or Department assignment to transactions already approved by a human. Writes to QuickBooks. Get the transaction list from preview_bulk_classification first — this tool only applies what you pass it. Max 100 per batch. On QuickBooks the class is written onto each line of a purchase, deposit or journal entry, and every record is checked after saving: a QuickBooks Transfer has no lines, and on a company that tracks class per line QuickBooks accepts the class and discards it, so such a transfer is reported as a failure naming that, never as updated. On Xero a class is a tracking-category option (pass its id or name) and there are no departments; bills, spend and receive money and manual journals can be classified, every line gets the option, and a line's tag in the organisation's OTHER tracking category is kept. A paid bill stays paid. Bank transfers cannot be classified after they are created, and a reconciled bank transaction is locked by Xero; both are reported individually rather than counted as failures.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"approved_transactions",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"class_ref": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200,
"description": "Display name"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO entity ID"
}
},
"description": "ClassRef to assign (value=ID, name=display name)",
"additionalProperties": false
},
"department_ref": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200,
"description": "Display name"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO entity ID"
}
},
"description": "DepartmentRef to assign (value=ID, name=display name)",
"additionalProperties": false
},
"approved_transactions": {
"type": "array",
"items": {
"type": "object",
"required": [
"entity_type",
"entity_id",
"sync_token"
],
"properties": {
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Transaction ID"
},
"sync_token": {
"type": "string",
"pattern": "^(\\d{1,10})?$",
"description": "SyncToken from preview results. Empty string for Xero, which has none."
},
"entity_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"JournalEntry",
"Bill"
],
"type": "string",
"description": "Transaction type. Bill is Xero only."
}
},
"additionalProperties": false
},
"maxItems": 100,
"description": "Transactions approved by human for classification (from preview_bulk_classification results)"
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Bulk Assign Classification",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Create a balanced journal entry in QuickBooks Online, or a manual journal in Xero. On Xero: PrivateNote is REQUIRED and becomes the journal Narration, which Xero rejects a journal without; the entry posts immediately (Status POSTED), matching what a QuickBooks journal entry means; DocNumber has no Xero home because Xero does not number manual journals; a line ClassRef is the class's tracking option (its id from search_classes, or its name) and is put on the line as tracking; and Adjustment, per-line Entity, DepartmentRef and TaxCodeRef-by-id are refused by name rather than dropped. Direction is preserved exactly: a Debit line posts as a positive Xero LineAmount, a Credit as a negative. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.
The description explains the capability, when to use it, and what to expect.
Inputs9/100
2 of 22 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › not_a_bank_line
Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book.
Clear enough to supply this argument.
params › journalEntry › Line › items › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › DetailType
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › AccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › type
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › TaxCodeRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › TaxCodeRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Adjustment
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_journal_entry",
"title": "Create Journal Entry",
"description": "Create a balanced journal entry in QuickBooks Online, or a manual journal in Xero. On Xero: PrivateNote is REQUIRED and becomes the journal Narration, which Xero rejects a journal without; the entry posts immediately (Status POSTED), matching what a QuickBooks journal entry means; DocNumber has no Xero home because Xero does not number manual journals; a line ClassRef is the class's tracking option (its id from search_classes, or its name) and is put on the line as tracking; and Adjustment, per-line Entity, DepartmentRef and TaxCodeRef-by-id are refused by name rather than dropped. Direction is preserved exactly: a Debit line posts as a positive Xero LineAmount, a Credit as a negative. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"journalEntry",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"journalEntry": {
"type": "object",
"required": [
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"DetailType",
"JournalEntryLineDetail"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"DetailType": {
"type": "string",
"const": "JournalEntryLineDetail"
},
"Description": {
"type": "string",
"maxLength": 4000
},
"JournalEntryLineDetail": {
"type": "object",
"required": [
"PostingType",
"AccountRef"
],
"properties": {
"Entity": {
"type": "object",
"required": [
"type",
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"type": {
"enum": [
"Customer",
"Vendor",
"Employee"
],
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
},
"TaxCodeRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
},
"PostingType": {
"enum": [
"Debit",
"Credit"
],
"type": "string"
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"maxItems": 200,
"minItems": 2
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"Adjustment": {
"type": "boolean"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
}
},
"additionalProperties": false
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book."
}
}
}
}
},
"annotations": {
"title": "Create Journal Entry",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Get a journal entry by Id from QuickBooks Online.On Xero this reads one ManualJournal. For several journal entries, use one search_journal_entries call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_journal_entry calls in parallel, which QuickBooks rate-limits (code 3001).
Describe the returned information so the agent knows whether it will answer the request.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_journal_entry",
"title": "Get Journal Entry",
"description": "Get a journal entry by Id from QuickBooks Online.On Xero this reads one ManualJournal. For several journal entries, use one search_journal_entries call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_journal_entry calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Journal Entry",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Update a balanced journal entry in QuickBooks Online.On Xero this is REFUSED: a posted manual journal is immutable there, and the only change Xero accepts is voiding. Void it with delete_journal_entry and post a corrected one - which is what a Xero bookkeeper does by hand, and the correction then carries its own number and date. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs12/100
4 of 25 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › journalEntry › Id
QBO JournalEntry ID
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › journalEntry › SyncToken
Optimistic concurrency token
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › journalEntry › sparse
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › DetailType
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › AccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › type
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › Entity › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › TaxCodeRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Line › items › JournalEntryLineDetail › TaxCodeRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › journalEntry › Adjustment
Not provided
Missing description. Explain what this value means and how to supply it.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Delete (make inactive) a journal entry in QuickBooks Online.On Xero a manual journal is VOIDED rather than deleted - the number and the entry stay in the books at zero, which is what an auditor expects to find. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
Resolve contradictions between the description, input schema, and annotations.
Inputs91/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_journal_entry",
"title": "Delete Journal Entry",
"description": "Delete (make inactive) a journal entry in QuickBooks Online.On Xero a manual journal is VOIDED rather than deleted - the number and the entry stay in the books at zero, which is what an auditor expects to find. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Journal Entry",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description74/100
Search journal entries in QuickBooks Online that match given criteria. On Xero this reads manual journals only, not the general ledger. Filter on Id, TxnDate or PrivateNote (Xero's Narration); DocNumber, Adjustment and ClassRef have no Xero equivalent and are refused by name.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online JournalEntry entity. One of: Id, TxnDate, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online JournalEntry entity. One of: Id, TxnDate, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_journal_entries",
"title": "Search Journal Entries",
"description": "Search journal entries in QuickBooks Online that match given criteria. On Xero this reads manual journals only, not the general ledger. Filter on Id, TxnDate or PrivateNote (Xero's Narration); DocNumber, Adjustment and ClassRef have no Xero equivalent and are refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online JournalEntry entity. One of: Id, TxnDate, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online JournalEntry entity. One of: Id, TxnDate, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Journal Entries",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Settle one or more open bills in QuickBooks Online. This debits Accounts Payable rather than an expense account, because whoever coded the bill already chose the expense. Use it whenever a payment discharges a bill; use create_purchase only when no bill was raised. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a Payment against the bill (Xero derives the ACCPAYPAYMENT type from the invoice, so PayType is not sent - it only selects which account reference we read, because Xero has no payment-method field and the account IS the method). ONE bill per call: Xero pays one invoice per payment, and its array write is not all-or-nothing, so a multi-bill payment is refused with the reason rather than risking some bills paid and an error returned. Passing a customer invoice id is refused by name rather than moving money the wrong way.
The description explains the capability, when to use it, and what to expect.
Inputs16/100
3 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › not_a_bank_line
Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book.
Clear enough to supply this argument.
params › billPayment › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › PayType
Payment method
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › billPayment › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › BankAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › BankAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › PrintStatus
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CreditCardPayment › CCAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CreditCardPayment › CCAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_bill_payment",
"title": "Create Bill Payment",
"description": "Settle one or more open bills in QuickBooks Online. This debits Accounts Payable rather than an expense account, because whoever coded the bill already chose the expense. Use it whenever a payment discharges a bill; use create_purchase only when no bill was raised. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a Payment against the bill (Xero derives the ACCPAYPAYMENT type from the invoice, so PayType is not sent - it only selects which account reference we read, because Xero has no payment-method field and the account IS the method). ONE bill per call: Xero pays one invoice per payment, and its array write is not all-or-nothing, so a multi-bill payment is refused with the reason rather than risking some bills paid and an error returned. Passing a customer invoice id is refused by name rather than moving money the wrong way.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"billPayment",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"billPayment": {
"type": "object",
"required": [
"VendorRef",
"PayType",
"TotalAmt",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"LinkedTxn"
],
"properties": {
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"LinkedTxn": {
"type": "array",
"items": {
"type": "object",
"required": [
"TxnId",
"TxnType"
],
"properties": {
"TxnId": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"TxnType": {
"type": "string",
"const": "Bill"
}
},
"additionalProperties": false
},
"maxItems": 10,
"minItems": 1
}
},
"additionalProperties": false
},
"maxItems": 200,
"minItems": 1,
"description": "Bill(s) or AP transactions being paid"
},
"PayType": {
"enum": [
"Check",
"CreditCard"
],
"type": "string",
"description": "Payment method"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Vendor being paid",
"additionalProperties": false
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"CheckPayment": {
"type": "object",
"required": [
"BankAccountRef"
],
"properties": {
"PrintStatus": {
"enum": [
"NotSet",
"NeedToPrint",
"PrintComplete"
],
"type": "string"
},
"BankAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"CreditCardPayment": {
"type": "object",
"required": [
"CCAccountRef"
],
"properties": {
"CCAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book."
}
}
}
}
},
"annotations": {
"title": "Create Bill Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Get a bill payment by Id from QuickBooks Online.On Xero this reads one Payment from the single Payments endpoint, filtered to the payable side. For several bill payments, use one search_bill_payments call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_bill_payment calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_bill_payment",
"title": "Get Bill Payment",
"description": "Get a bill payment by Id from QuickBooks Online.On Xero this reads one Payment from the single Payments endpoint, filtered to the payable side. For several bill payments, use one search_bill_payments call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_bill_payment calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Bill Payment",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get one customer payment (a received payment applied to invoices) by Id from QuickBooks Online, with its SyncToken for update_payment. LinkedTxn on the payment itself shows the deposit it has been banked on as TxnType "Deposit"; DepositToAccountRef is the account it was received into, which is Undeposited Funds until it is banked. To FIND a payment, use search_bank_transactions on the account it was received into -- the Undeposited Funds account for one that has not been banked yet -- or the invoice it settles. For several payments, read them one at a time or list them with search_bank_transactions: many get_payment calls in parallel are rate-limited by QuickBooks (code 3001). On Xero this reads one Payment from the single Payments endpoint (a customer payment is ACCRECPAYMENT); Xero has no Undeposited Funds, so a Xero payment is always in a bank account already.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_payment",
"title": "Get Payment",
"description": "Get one customer payment (a received payment applied to invoices) by Id from QuickBooks Online, with its SyncToken for update_payment. LinkedTxn on the payment itself shows the deposit it has been banked on as TxnType \"Deposit\"; DepositToAccountRef is the account it was received into, which is Undeposited Funds until it is banked. To FIND a payment, use search_bank_transactions on the account it was received into -- the Undeposited Funds account for one that has not been banked yet -- or the invoice it settles. For several payments, read them one at a time or list them with search_bank_transactions: many get_payment calls in parallel are rate-limited by QuickBooks (code 3001). On Xero this reads one Payment from the single Payments endpoint (a customer payment is ACCRECPAYMENT); Xero has no Undeposited Funds, so a Xero payment is always in a bank account already.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Payment",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Update a bill payment in QuickBooks Online. Updates are sparse: send Id, SyncToken and only the fields being changed, not the whole record from get_bill_payment - omitting a field never changes it, and a payment scheduled through QuickBooks Bill Pay refuses any change to its payee, account, date, mailing address or amount. Not available for Xero companies: Xero cannot update a payment at all - delete it and record it again. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs14/100
4 of 20 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › billPayment › Id
QBO BillPayment ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › billPayment › SyncToken
Optimistic concurrency token
Explain the meaning of this value, not just its name.
params › billPayment › sparse
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › PayType
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › BankAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › BankAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CheckPayment › PrintStatus
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CreditCardPayment › CCAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › CreditCardPayment › CCAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › billPayment › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_bill_payment",
"title": "Update Bill Payment",
"description": "Update a bill payment in QuickBooks Online. Updates are sparse: send Id, SyncToken and only the fields being changed, not the whole record from get_bill_payment - omitting a field never changes it, and a payment scheduled through QuickBooks Bill Pay refuses any change to its payee, account, date, mailing address or amount. Not available for Xero companies: Xero cannot update a payment at all - delete it and record it again. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"billPayment",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"billPayment": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO BillPayment ID"
},
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"LinkedTxn"
],
"properties": {
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"LinkedTxn": {
"type": "array",
"items": {
"type": "object",
"required": [
"TxnId",
"TxnType"
],
"properties": {
"TxnId": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"TxnType": {
"type": "string",
"const": "Bill"
}
},
"additionalProperties": false
},
"maxItems": 10,
"minItems": 1
}
},
"additionalProperties": false
},
"maxItems": 200,
"minItems": 1
},
"sparse": {
"type": "boolean",
"const": true
},
"PayType": {
"enum": [
"Check",
"CreditCard"
],
"type": "string"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"CheckPayment": {
"type": "object",
"required": [
"BankAccountRef"
],
"properties": {
"PrintStatus": {
"enum": [
"NotSet",
"NeedToPrint",
"PrintComplete"
],
"type": "string"
},
"BankAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"CreditCardPayment": {
"type": "object",
"required": [
"CCAccountRef"
],
"properties": {
"CCAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Bill Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Delete (make inactive) a bill payment in QuickBooks Online.On Xero the payment is DELETED, which is how Xero reverses one - it states payments cannot be modified, only created and deleted. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
Resolve contradictions between the description, input schema, and annotations.
Inputs93/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_bill_payment",
"title": "Delete Bill Payment",
"description": "Delete (make inactive) a bill payment in QuickBooks Online.On Xero the payment is DELETED, which is how Xero reverses one - it states payments cannot be modified, only created and deleted. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Bill Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description65/100
Search bill payments in QuickBooks Online that match given criteria.On Xero this reads the single Payments endpoint filtered to ACCPAYPAYMENT - Xero has one payment object for both directions and derives the type from the invoice paid. Filter on Id, TxnDate or TotalAmt; VendorRef has no Xero equivalent (a payment carries the invoice, not the contact) and is refused by name.
Resolve contradictions between the description, input schema, and annotations.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online BillPayment entity. One of: Id, TxnDate, TotalAmt, VendorRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online BillPayment entity. One of: Id, TxnDate, TotalAmt, VendorRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_bill_payments",
"title": "Search Bill Payments",
"description": "Search bill payments in QuickBooks Online that match given criteria.On Xero this reads the single Payments endpoint filtered to ACCPAYPAYMENT - Xero has one payment object for both directions and derives the type from the invoice paid. Filter on Id, TxnDate or TotalAmt; VendorRef has no Xero equivalent (a payment carries the invoice, not the contact) and is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online BillPayment entity. One of: Id, TxnDate, TotalAmt, VendorRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online BillPayment entity. One of: Id, TxnDate, TotalAmt, VendorRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Bill Payments",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Create a purchase in QuickBooks Online: an expense paid directly from a bank or credit-card account, by cash, cheque or card. Use it when money left an account and no bill was raised first. If a bill exists, settle it with create_bill_payment instead, or the expense is counted twice - once on the bill and once here. A refund on a credit card is a Purchase with Credit: true, not a deposit. ClassRef goes INSIDE each line's AccountBasedExpenseLineDetail object, next to AccountRef; set it whenever the company tracks classes. DepartmentRef is a DOCUMENT-level field: put it on the purchase, never on a line, which accepts it in neither position. Measured 2026-09-10: either one in the wrong place fails the whole request with code 2010. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a BankTransaction of type SPEND (spend money). EntityRef is REQUIRED here even though QuickBooks treats a payee as optional - Xero refuses a spend with no contact - so a purchase without one is refused by name rather than by Xero's own message, which does not say which field is missing. PaymentType has no Xero field at all: the method is implied by the account the money leaves, which AccountRef already names. Class and department tracking, billable expenses and TaxCodeRef-by-id are refused by name. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does.
The description explains the capability, when to use it, and what to expect.
Inputs29/100
4 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › not_a_bank_line
Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book.
Clear enough to supply this argument.
params › purchase › PaymentType
Payment method
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase › AccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › Line
At least one line item required. Each line's AccountBasedExpenseLineDetail.AccountRef.value must be the account's Id -- a short numeric string such as "21" -- and NEVER its name: the account name there is refused as "Invalid Number" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › EntityRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › EntityRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › EntityRef › type
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_purchase",
"title": "Create Purchase",
"description": "Create a purchase in QuickBooks Online: an expense paid directly from a bank or credit-card account, by cash, cheque or card. Use it when money left an account and no bill was raised first. If a bill exists, settle it with create_bill_payment instead, or the expense is counted twice - once on the bill and once here. A refund on a credit card is a Purchase with Credit: true, not a deposit. ClassRef goes INSIDE each line's AccountBasedExpenseLineDetail object, next to AccountRef; set it whenever the company tracks classes. DepartmentRef is a DOCUMENT-level field: put it on the purchase, never on a line, which accepts it in neither position. Measured 2026-09-10: either one in the wrong place fails the whole request with code 2010. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a BankTransaction of type SPEND (spend money). EntityRef is REQUIRED here even though QuickBooks treats a payee as optional - Xero refuses a spend with no contact - so a purchase without one is refused by name rather than by Xero's own message, which does not say which field is missing. PaymentType has no Xero field at all: the method is implied by the account the money leaves, which AccountRef already names. Class and department tracking, billable expenses and TaxCodeRef-by-id are refused by name. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"purchase",
"realm_id"
],
"properties": {
"purchase": {
"type": "object",
"required": [
"PaymentType",
"AccountRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required. Each line's AccountBasedExpenseLineDetail.AccountRef.value must be the account's Id -- a short numeric string such as \"21\" -- and NEVER its name: the account name there is refused as \"Invalid Number\" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number"
},
"EntityRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"type": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank or credit card account"
},
"PaymentType": {
"enum": [
"Cash",
"Check",
"CreditCard"
],
"type": "string",
"description": "Payment method"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book."
}
}
}
}
},
"annotations": {
"title": "Create Purchase",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
Get a purchase by Id from QuickBooks Online.On Xero this reads one spend money (SPEND) bank transaction. A receive money (RECEIVE) id is refused by name rather than returned as a purchase. For several purchases, use one search_purchases call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_purchase calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_purchase",
"title": "Get Purchase",
"description": "Get a purchase by Id from QuickBooks Online.On Xero this reads one spend money (SPEND) bank transaction. A receive money (RECEIVE) id is refused by name rather than returned as a purchase. For several purchases, use one search_purchases call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_purchase calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Purchase",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Update a purchase in QuickBooks Online.On Xero this updates the spend money (SPEND) bank transaction -- this is the tool that RECODES one. A receive money (RECEIVE) id is refused by name: update_sales_receipt is the one for those. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does. QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs32/100
5 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › purchase › Id
QBO Purchase ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › purchase › SyncToken
Optimistic concurrency token
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase › Line
Each line's AccountBasedExpenseLineDetail.AccountRef.value must be the account's Id -- a short numeric string such as "21" -- and NEVER its name: the account name there is refused as "Invalid Number" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase › AccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › AccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › PaymentType
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_purchase",
"title": "Update Purchase",
"description": "Update a purchase in QuickBooks Online.On Xero this updates the spend money (SPEND) bank transaction -- this is the tool that RECODES one. A receive money (RECEIVE) id is refused by name: update_sales_receipt is the one for those. The customer on an expense line is CustomerRef inside that same AccountBasedExpenseLineDetail: the field named Entity is a DEPOSIT-line field and QuickBooks rejects the whole request for it here (code 2010, measured 2026-09-12), which is what a shape copied from create_deposit does. QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"purchase",
"realm_id"
],
"properties": {
"purchase": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Purchase ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Each line's AccountBasedExpenseLineDetail.AccountRef.value must be the account's Id -- a short numeric string such as \"21\" -- and NEVER its name: the account name there is refused as \"Invalid Number\" (code 2090) quoting the name back at you, which reads as a complaint about the amount and is not one. Look the id up with search_accounts."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token"
},
"AccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
}
},
"PaymentType": {
"enum": [
"Cash",
"Check",
"CreditCard"
],
"type": "string"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Purchase",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Delete a purchase in QuickBooks Online - the expense is removed, not made inactive. On Xero the transaction is transitioned to DELETED rather than deleted, so the record stays retrievable. QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_purchase",
"title": "Delete Purchase",
"description": "Delete a purchase in QuickBooks Online - the expense is removed, not made inactive. On Xero the transaction is transitioned to DELETED rather than deleted, so the record stays retrievable. QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Purchase",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description77/100
Search purchases in QuickBooks Online that match given criteria.On Xero this reads BankTransactions filtered to SPEND (spend money). Filter on Id, TxnDate, TotalAmt or DocNumber (Xero's Reference). PaymentType has no Xero equivalent - the method is implied by the account - and is refused by name rather than ignored, because a silently dropped PaymentType filter would return cash and cheque purchases too while reading as filtered.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Purchase entity. One of: Id, TxnDate, TotalAmt, PaymentType, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Purchase entity. One of: Id, TxnDate, TotalAmt, PaymentType, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_purchases",
"title": "Search Purchases",
"description": "Search purchases in QuickBooks Online that match given criteria.On Xero this reads BankTransactions filtered to SPEND (spend money). Filter on Id, TxnDate, TotalAmt or DocNumber (Xero's Reference). PaymentType has no Xero equivalent - the method is implied by the account - and is refused by name rather than ignored, because a silently dropped PaymentType filter would return cash and cheque purchases too while reading as filtered.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Purchase entity. One of: Id, TxnDate, TotalAmt, PaymentType, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Purchase entity. One of: Id, TxnDate, TotalAmt, PaymentType, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused.PaymentType must be one of: Cash, Check, CreditCard (CreditCard is one word). Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Purchases",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Create a sales receipt in QuickBooks Online. Use for revenue paid at the time of sale: cash sale, card payment, point of sale, Stripe charge. Records revenue and cash on ONE document with no accounts receivable. Do NOT use create_invoice plus create_payment for a paid-on-the-spot sale: that opens and closes a receivable the same day and pollutes AR aging.On Xero this writes a BankTransaction of type RECEIVE (receive money). Two QuickBooks habits are refused by name rather than approximated: a contact is REQUIRED (Xero has no anonymous receipt), and the money must land in a real bank account (Xero has no Undeposited Funds to group later - it groups at reconciliation instead). What is lost is stated plainly: a Xero receipt has no document number of its own, no PDF and no email. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
Resolve contradictions between the description, input schema, and annotations.
Inputs16/100
3 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › sales_receipt › Line
At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sales_receipt › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PaymentMethodRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PaymentMethodRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TxnTaxDetail
Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_sales_receipt",
"title": "Create Sales Receipt",
"description": "Create a sales receipt in QuickBooks Online. Use for revenue paid at the time of sale: cash sale, card payment, point of sale, Stripe charge. Records revenue and cash on ONE document with no accounts receivable. Do NOT use create_invoice plus create_payment for a paid-on-the-spot sale: that opens and closes a receivable the same day and pollutes AR aging.On Xero this writes a BankTransaction of type RECEIVE (receive money). Two QuickBooks habits are refused by name rather than approximated: a contact is REQUIRED (Xero has no anonymous receipt), and the money must land in a real bank account (Xero has no Undeposited Funds to group later - it groups at reconciliation instead). What is lost is stated plainly: a Xero receipt has no document number of its own, no PDF and no email. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"sales_receipt",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"sales_receipt": {
"type": "object",
"required": [
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer who bought. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"PaymentMethodRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money landed in. Omit to route to Undeposited Funds."
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Sales Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Get a sales receipt by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_sales_receipt and delete_sales_receipt both require.On Xero this reads one receive money (RECEIVE) bank transaction. A spend money (SPEND) id is refused by name rather than returned. For several sales receipts, use one search_sales_receipts call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_sales_receipt calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_sales_receipt",
"title": "Get Sales Receipt",
"description": "Get a sales receipt by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_sales_receipt and delete_sales_receipt both require.On Xero this reads one receive money (RECEIVE) bank transaction. A spend money (SPEND) id is refused by name rather than returned. For several sales receipts, use one search_sales_receipts call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_sales_receipt calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Sales Receipt",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description76/100
Update a sales receipt in QuickBooks Online. Requires Id and a current SyncToken from get_sales_receipt. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the receive money (RECEIVE) bank transaction -- this is the tool that RECODES one, the counterpart of update_purchase for spend money. A spend money (SPEND) id is refused by name. To change the account a receive money line is coded to, send Line with the line's LineItemID and the AccountCode you want; lines are replaced wholesale, so send them all. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
Resolve contradictions between the description, input schema, and annotations.
Inputs26/100
6 of 20 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › sales_receipt › Id
QBO SalesReceipt ID
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sales_receipt › SyncToken
Optimistic concurrency token from get_sales_receipt
Clear enough to supply this argument.
params › sales_receipt › Line
Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sales_receipt › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PaymentMethodRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PaymentMethodRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › sales_receipt › TxnTaxDetail
Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_sales_receipt",
"title": "Update Sales Receipt",
"description": "Update a sales receipt in QuickBooks Online. Requires Id and a current SyncToken from get_sales_receipt. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the receive money (RECEIVE) bank transaction -- this is the tool that RECODES one, the counterpart of update_purchase for spend money. A spend money (SPEND) id is refused by name. To change the account a receive money line is coded to, send Line with the line's LineItemID and the AccountCode you want; lines are replaced wholesale, so send them all. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"sales_receipt",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"sales_receipt": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO SalesReceipt ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_sales_receipt"
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer who bought. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"PaymentMethodRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money landed in. Omit to route to Undeposited Funds."
}
},
"additionalProperties": {}
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Sales Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Delete a sales receipt in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the transaction is transitioned to DELETED rather than deleted. A spend money (SPEND) id is refused by name. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_sales_receipt",
"title": "Delete Sales Receipt",
"description": "Delete a sales receipt in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the transaction is transitioned to DELETED rather than deleted. A spend money (SPEND) id is refused by name. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Sales Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Search sales receipts in QuickBooks Online that match given criteria. Use this to find an existing sales receipt before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads BankTransactions filtered to RECEIVE (receive money). A Xero receipt has no document number of its own, no PDF and no email -- those are named here rather than discovered later. CustomerRef cannot be filtered on (the contact is a nested object) and is refused by name.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online SalesReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime, PaymentRefNum. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online SalesReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime, PaymentRefNum. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_sales_receipts",
"title": "Search Sales Receipts",
"description": "Search sales receipts in QuickBooks Online that match given criteria. Use this to find an existing sales receipt before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads BankTransactions filtered to RECEIVE (receive money). A Xero receipt has no document number of its own, no PDF and no email -- those are named here rather than discovered later. CustomerRef cannot be filtered on (the contact is a nested object) and is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online SalesReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime, PaymentRefNum. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online SalesReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime, PaymentRefNum. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Sales Receipts",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Create a credit memo in QuickBooks Online. Use when a customer owes LESS than billed: overcharge, returned goods, goodwill adjustment, write down an invoice. Does NOT apply itself to the invoice: call apply_credit_memo afterwards or both documents stay open in AR aging. Do NOT use a reversing journal entry for this, a JE is invisible to AR aging and cannot be applied.On Xero this writes a CreditNote of type ACCRECCREDIT. Line detail comes from SalesItemLineDetail: give ItemRef or AccountRef on every line, and give Qty and UnitPrice together or neither (a Qty without a UnitPrice would make Xero multiply the line total by the quantity, so it is refused). ClassRef, DepartmentRef and TxnTaxDetail have no Xero equivalent and are refused by name - Xero computes tax from each line's TaxType and has no document-level override. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs21/100
3 of 13 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › credit_memo › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › Line
At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › credit_memo › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › TxnTaxDetail
Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_credit_memo",
"title": "Create Credit Memo",
"description": "Create a credit memo in QuickBooks Online. Use when a customer owes LESS than billed: overcharge, returned goods, goodwill adjustment, write down an invoice. Does NOT apply itself to the invoice: call apply_credit_memo afterwards or both documents stay open in AR aging. Do NOT use a reversing journal entry for this, a JE is invisible to AR aging and cannot be applied.On Xero this writes a CreditNote of type ACCRECCREDIT. Line detail comes from SalesItemLineDetail: give ItemRef or AccountRef on every line, and give Qty and UnitPrice together or neither (a Qty without a UnitPrice would make Xero multiply the line total by the quantity, so it is refused). ClassRef, DepartmentRef and TxnTaxDetail have no Xero equivalent and are refused by name - Xero computes tax from each line's TaxType and has no document-level override. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"credit_memo",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"credit_memo": {
"type": "object",
"required": [
"CustomerRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer being credited. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Credit Memo",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get a credit memo by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_credit_memo and delete_credit_memo both require.On Xero this reads one CreditNote. A supplier credit note id is refused by name rather than returned, because Xero keeps both kinds on one endpoint and the id is valid for the other one. For several credit memos, use one search_credit_memos call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_credit_memo calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_credit_memo",
"title": "Get Credit Memo",
"description": "Get a credit memo by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_credit_memo and delete_credit_memo both require.On Xero this reads one CreditNote. A supplier credit note id is refused by name rather than returned, because Xero keeps both kinds on one endpoint and the id is valid for the other one. For several credit memos, use one search_credit_memos call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_credit_memo calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Credit Memo",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Update a credit memo in QuickBooks Online. Requires Id and a current SyncToken from get_credit_memo. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the customer CreditNote. A supplier credit note id is refused by name rather than rewriting the wrong document. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs28/100
5 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › credit_memo › Id
QBO CreditMemo ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › credit_memo › SyncToken
Optimistic concurrency token from get_credit_memo
Clear enough to supply this argument.
params › credit_memo › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › Line
Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › credit_memo › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › credit_memo › TxnTaxDetail
Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_credit_memo",
"title": "Update Credit Memo",
"description": "Update a credit memo in QuickBooks Online. Requires Id and a current SyncToken from get_credit_memo. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the customer CreditNote. A supplier credit note id is refused by name rather than rewriting the wrong document. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"credit_memo",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"credit_memo": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO CreditMemo ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_credit_memo"
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer being credited. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Update Credit Memo",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Delete a credit memo in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero a credit note is transitioned to DELETED or VOIDED depending on its status, not deleted. A supplier credit note id is refused by name.
The description explains the capability, when to use it, and what to expect.
Inputs91/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_credit_memo",
"title": "Delete Credit Memo",
"description": "Delete a credit memo in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero a credit note is transitioned to DELETED or VOIDED depending on its status, not deleted. A supplier credit note id is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
}
}
}
}
},
"annotations": {
"title": "Delete Credit Memo",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Search credit memos in QuickBooks Online that match given criteria. Use this to find an existing credit memo before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads CreditNotes filtered to ACCRECCREDIT -- Xero keeps customer and supplier credit notes on one endpoint, split by type. Filter on Id, DocNumber, TxnDate, TotalAmt or Balance (Xero's RemainingCredit, what is still unapplied). ClassRef has no Xero equivalent and is refused by name.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online CreditMemo entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, Balance, RemainingCredit, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online CreditMemo entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, Balance, RemainingCredit, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_credit_memos",
"title": "Search Credit Memos",
"description": "Search credit memos in QuickBooks Online that match given criteria. Use this to find an existing credit memo before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads CreditNotes filtered to ACCRECCREDIT -- Xero keeps customer and supplier credit notes on one endpoint, split by type. Filter on Id, DocNumber, TxnDate, TotalAmt or Balance (Xero's RemainingCredit, what is still unapplied). ClassRef has no Xero equivalent and is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online CreditMemo entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, Balance, RemainingCredit, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online CreditMemo entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, Balance, RemainingCredit, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Credit Memos",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Apply an existing credit memo to one or more open invoices in QuickBooks Online. This is the SECOND HALF of every credit memo: QuickBooks does not link a credit memo to the invoice by itself, so a credit created and not applied leaves both documents open in AR aging and the customer balance uncorrected. Call this immediately after create_credit_memo, in the same approval. Reports the credit's remaining balance afterwards so you can confirm the application actually landed.On Xero this writes an Allocation against the credit note. ONE invoice per call: Xero's array writes are not all-or-nothing, so a multi-invoice allocation that failed partway would spend part of the credit and still report an error. Applying a customer credit to a supplier bill is refused by name. txn_date and private_note have no Xero equivalent - an allocation is dated today and carries no note - and are refused rather than dropped.
Resolve contradictions between the description, input schema, and annotations.
Inputs67/100
4 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › credit_memo_id
Id of an existing credit memo. Find it with search_credit_memos.
Clear enough to supply this argument.
params › applications › items › invoice_id
Open invoice this credit offsets. Find it with search_invoices.
Clear enough to supply this argument.
params › applications › items › amount
How much of the credit to apply to this invoice. Partial is normal.
Clear enough to supply this argument.
params › txn_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › private_note
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "apply_credit_memo",
"title": "Apply Credit Memo",
"description": "Apply an existing credit memo to one or more open invoices in QuickBooks Online. This is the SECOND HALF of every credit memo: QuickBooks does not link a credit memo to the invoice by itself, so a credit created and not applied leaves both documents open in AR aging and the customer balance uncorrected. Call this immediately after create_credit_memo, in the same approval. Reports the credit's remaining balance afterwards so you can confirm the application actually landed.On Xero this writes an Allocation against the credit note. ONE invoice per call: Xero's array writes are not all-or-nothing, so a multi-invoice allocation that failed partway would spend part of the credit and still report an error. Applying a customer credit to a supplier bill is refused by name. txn_date and private_note have no Xero equivalent - an allocation is dated today and carries no note - and are refused rather than dropped.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"credit_memo_id",
"applications",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"txn_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"applications": {
"type": "array",
"items": {
"type": "object",
"required": [
"invoice_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"maximum": 999999999.99,
"description": "How much of the credit to apply to this invoice. Partial is normal.",
"exclusiveMinimum": 0
},
"invoice_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Open invoice this credit offsets. Find it with search_invoices."
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "One entry per invoice being offset."
},
"private_note": {
"type": "string",
"maxLength": 4000
},
"credit_memo_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of an existing credit memo. Find it with search_credit_memos."
}
}
}
}
},
"annotations": {
"title": "Apply Credit Memo",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Remove a credit note's allocation from a customer invoice in Xero, putting the credit back and returning the invoice to AUTHORISED with its full amount owing. This is the undo of apply_credit_memo, and the way to void an invoice that Xero refuses to void because a credit note is allocated to it: unapply the credit, then call void_invoice. Measured: the invoice goes straight back to AUTHORISED with AmountDue restored and the credit note's remaining balance goes back up. It works the same for a supplier credit note allocated to a bill (pass the bill as invoice_id; measured), and it is the first step of editing an allocated credit note, which Xero refuses outright: unapply, update_credit_memo / update_vendor_credit, then apply_credit_memo / apply_vendor_credit again. Name the two documents - the credit note and the invoice - and this finds the allocation between them, so a credit note spread over several invoices only loses the one you name. QuickBooks has no allocation to remove: there a credit memo is applied by a separate Payment carrying both as LinkedTxn entries, so undo it with void_payment on that Payment, and this tool says so rather than acting.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › credit_memo_id
Id of the credit note whose allocation is being removed. Find it with search_credit_memos.
Clear enough to supply this argument.
params › invoice_id
Id of the invoice it is allocated to. Find it with search_invoices or read_invoice.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "unapply_credit_memo",
"title": "Unapply Credit Memo",
"description": "Remove a credit note's allocation from a customer invoice in Xero, putting the credit back and returning the invoice to AUTHORISED with its full amount owing. This is the undo of apply_credit_memo, and the way to void an invoice that Xero refuses to void because a credit note is allocated to it: unapply the credit, then call void_invoice. Measured: the invoice goes straight back to AUTHORISED with AmountDue restored and the credit note's remaining balance goes back up. It works the same for a supplier credit note allocated to a bill (pass the bill as invoice_id; measured), and it is the first step of editing an allocated credit note, which Xero refuses outright: unapply, update_credit_memo / update_vendor_credit, then apply_credit_memo / apply_vendor_credit again. Name the two documents - the credit note and the invoice - and this finds the allocation between them, so a credit note spread over several invoices only loses the one you name. QuickBooks has no allocation to remove: there a credit memo is applied by a separate Payment carrying both as LinkedTxn entries, so undo it with void_payment on that Payment, and this tool says so rather than acting.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"credit_memo_id",
"invoice_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"invoice_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the invoice it is allocated to. Find it with search_invoices or read_invoice."
},
"credit_memo_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the credit note whose allocation is being removed. Find it with search_credit_memos."
}
}
}
}
},
"annotations": {
"title": "Unapply Credit Memo",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Create a refund receipt in QuickBooks Online. Use when CASH actually went back to a customer: refund, money returned, reimbursement of a sale. If no money moved and the customer simply owes less, use create_credit_memo instead. A refund receipt is its own document, NOT a reversal of a sales receipt.On Xero this writes a BankTransaction of type SPEND to the customer - money leaving the bank, coded to the account the original sale credited. That is the faithful shape for a QuickBooks refund receipt, which refunds a sale that was itself a receipt with no invoice involved. If the refund belongs against an INVOICE, use create_credit_memo and apply_credit_memo instead - that is a different document and this tool will not quietly stand in for it.
The description explains the capability, when to use it, and what to expect.
Inputs16/100
3 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › refund_receipt › Line
At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › refund_receipt › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PaymentMethodRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PaymentMethodRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TxnTaxDetail
Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_refund_receipt",
"title": "Create Refund Receipt",
"description": "Create a refund receipt in QuickBooks Online. Use when CASH actually went back to a customer: refund, money returned, reimbursement of a sale. If no money moved and the customer simply owes less, use create_credit_memo instead. A refund receipt is its own document, NOT a reversal of a sales receipt.On Xero this writes a BankTransaction of type SPEND to the customer - money leaving the bank, coded to the account the original sale credited. That is the faithful shape for a QuickBooks refund receipt, which refunds a sale that was itself a receipt with no invoice involved. If the refund belongs against an INVOICE, use create_credit_memo and apply_credit_memo instead - that is a different document and this tool will not quietly stand in for it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"refund_receipt",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"refund_receipt": {
"type": "object",
"required": [
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required. On a company with sales tax enabled, set SalesItemLineDetail.TaxCodeRef (TAX, or a specific tax code) on every taxable line - WITHOUT it QuickBooks defaults the line to NON and posts the document with ZERO tax, even for a taxable customer."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer being refunded. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through UNCHANGED and UNVALIDATED. Measured against a live automated-sales-tax company: a TotalTax of 999.99 on a 100.00 sale was accepted verbatim, so a wrong number here lands in the client tax return. Prefer omitting this and setting TaxCodeRef on each line instead, which makes QuickBooks calculate the tax itself. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"PaymentMethodRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money left FROM."
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Refund Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Get a refund receipt by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_refund_receipt and delete_refund_receipt both require.On Xero this reads one spend money (SPEND) bank transaction. Xero does not distinguish a customer refund from a supplier purchase at the endpoint - the contact is what differs - so a purchase id will also read here. For several refund receipts, use one search_refund_receipts call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_refund_receipt calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_refund_receipt",
"title": "Get Refund Receipt",
"description": "Get a refund receipt by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_refund_receipt and delete_refund_receipt both require.On Xero this reads one spend money (SPEND) bank transaction. Xero does not distinguish a customer refund from a supplier purchase at the endpoint - the contact is what differs - so a purchase id will also read here. For several refund receipts, use one search_refund_receipts call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_refund_receipt calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Refund Receipt",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description81/100
Update a refund receipt in QuickBooks Online. Requires Id and a current SyncToken from get_refund_receipt. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the spend money (SPEND) bank transaction. Id is required; SyncToken is ignored. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs24/100
6 of 20 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › refund_receipt › Id
QBO RefundReceipt ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › refund_receipt › SyncToken
Optimistic concurrency token from get_refund_receipt
Clear enough to supply this argument.
params › refund_receipt › Line
Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › refund_receipt › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PaymentMethodRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PaymentMethodRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › refund_receipt › TxnTaxDetail
Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_refund_receipt",
"title": "Update Refund Receipt",
"description": "Update a refund receipt in QuickBooks Online. Requires Id and a current SyncToken from get_refund_receipt. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the spend money (SPEND) bank transaction. Id is required; SyncToken is ignored. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"refund_receipt",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"refund_receipt": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO RefundReceipt ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_refund_receipt"
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer being refunded. Look up with search_customers first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"TxnTaxDetail": {
"type": "object",
"properties": {},
"description": "Sales tax detail, passed through unchanged. Only for companies with sales tax enabled; omit otherwise. We do not calculate tax.",
"additionalProperties": {}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"PaymentMethodRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money left FROM."
}
},
"additionalProperties": {}
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Refund Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Delete a refund receipt in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the transaction is transitioned to DELETED rather than deleted. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_refund_receipt",
"title": "Delete Refund Receipt",
"description": "Delete a refund receipt in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the transaction is transitioned to DELETED rather than deleted. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Refund Receipt",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Search refund receipts in QuickBooks Online that match given criteria. Use this to find an existing refund receipt before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads BankTransactions filtered to SPEND (spend money). Xero does not separate a customer refund from a supplier purchase at the endpoint - only the contact differs, and its query language cannot filter on that - so this returns the same rows as search_purchases. Match on the contact locally.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online RefundReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online RefundReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_refund_receipts",
"title": "Search Refund Receipts",
"description": "Search refund receipts in QuickBooks Online that match given criteria. Use this to find an existing refund receipt before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads BankTransactions filtered to SPEND (spend money). Xero does not separate a customer refund from a supplier purchase at the endpoint - only the contact differs, and its query language cannot filter on that - so this returns the same rows as search_purchases. Match on the contact locally.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online RefundReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online RefundReceipt entity. One of: Id, TxnDate, TotalAmt, CustomerRef, DocNumber, ClassRef, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Refund Receipts",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Create a purchase order in QuickBooks Online. Records a commitment to buy from a vendor. NON-POSTING: a PO never touches the general ledger, so it will NOT appear on a profit and loss, balance sheet, or trial balance, and does not affect accounts payable until it becomes a bill. Convert it with convert_purchase_order_to_bill, which closes the PO; a bill raised separately leaves the PO open forever.On Xero this writes a PurchaseOrder, created AUTHORISED to match create_bill - a QuickBooks purchase order is a real document the supplier is meant to see, not a draft. Lines follow the bill rules, because a purchase order codes to the accounts the bill it becomes will. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs17/100
3 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › purchase_order › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › Line
At least one line item required
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase_order › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › POStatus
Open by default. Closed means fully received or manually closed.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase_order › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_purchase_order",
"title": "Create Purchase Order",
"description": "Create a purchase order in QuickBooks Online. Records a commitment to buy from a vendor. NON-POSTING: a PO never touches the general ledger, so it will NOT appear on a profit and loss, balance sheet, or trial balance, and does not affect accounts payable until it becomes a bill. Convert it with convert_purchase_order_to_bill, which closes the PO; a bill raised separately leaves the PO open forever.On Xero this writes a PurchaseOrder, created AUTHORISED to match create_bill - a QuickBooks purchase order is a real document the supplier is meant to see, not a draft. Lines follow the bill rules, because a purchase order codes to the accounts the bill it becomes will. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"purchase_order",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"purchase_order": {
"type": "object",
"required": [
"VendorRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"POStatus": {
"enum": [
"Open",
"Closed"
],
"type": "string",
"description": "Open by default. Closed means fully received or manually closed."
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Vendor being ordered from. Look up with search_vendors first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Purchase Order",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Get a purchase order by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_purchase_order and delete_purchase_order both require.On Xero this reads one PurchaseOrder. For several purchase orders, use one search_purchase_orders call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_purchase_order calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_purchase_order",
"title": "Get Purchase Order",
"description": "Get a purchase order by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_purchase_order and delete_purchase_order both require.On Xero this reads one PurchaseOrder. For several purchase orders, use one search_purchase_orders call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_purchase_order calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Purchase Order",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Update a purchase order in QuickBooks Online. Requires Id and a current SyncToken from get_purchase_order. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the PurchaseOrder. Id is required; SyncToken is ignored. Sending Line replaces every line. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.
The description explains the capability, when to use it, and what to expect.
Inputs28/100
5 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › purchase_order › Id
QBO PurchaseOrder ID
Clear enough to supply this argument.
params › purchase_order › SyncToken
Optimistic concurrency token from get_purchase_order
Clear enough to supply this argument.
params › purchase_order › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › Line
Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › purchase_order › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › POStatus
Open by default. Closed means fully received or manually closed.
Clear enough to supply this argument.
params › purchase_order › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › purchase_order › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_purchase_order",
"title": "Update Purchase Order",
"description": "Update a purchase order in QuickBooks Online. Requires Id and a current SyncToken from get_purchase_order. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the PurchaseOrder. Id is required; SyncToken is ignored. Sending Line replaces every line. Recipient fields (BillEmail, BillEmailCc, BillEmailBcc, POEmail) are refused with recipient_field_refused: set the customer's or vendor's email, or pass send_to on the send.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"purchase_order",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"purchase_order": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO PurchaseOrder ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"POStatus": {
"enum": [
"Open",
"Closed"
],
"type": "string",
"description": "Open by default. Closed means fully received or manually closed."
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_purchase_order"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Vendor being ordered from. Look up with search_vendors first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Update Purchase Order",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Delete a purchase order in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the order is transitioned to DELETED rather than deleted.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Input documentation gives an agent enough context to populate the arguments.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_purchase_order",
"title": "Delete Purchase Order",
"description": "Delete a purchase order in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero the order is transitioned to DELETED rather than deleted.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
}
}
}
}
},
"annotations": {
"title": "Delete Purchase Order",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Search purchase orders in QuickBooks Online that match given criteria. Use this to find an existing purchase order before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads PurchaseOrders. Filter on Id, DocNumber (PurchaseOrderNumber), TxnDate or TotalAmt; VendorRef is a nested object Xero cannot filter on and is refused by name.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online PurchaseOrder entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online PurchaseOrder entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_purchase_orders",
"title": "Search Purchase Orders",
"description": "Search purchase orders in QuickBooks Online that match given criteria. Use this to find an existing purchase order before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads PurchaseOrders. Filter on Id, DocNumber (PurchaseOrderNumber), TxnDate or TotalAmt; VendorRef is a nested object Xero cannot filter on and is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online PurchaseOrder entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online PurchaseOrder entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Purchase Orders",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Convert a purchase order into a bill in QuickBooks Online and close the PO in one step. ALWAYS use this to bill against a PO. A bill created separately with create_bill looks completely correct - the expense posts and the vendor gets paid - but leaves the purchase order open indefinitely with no visible symptom. QuickBooks' API cannot link a bill to a purchase order (the link QuickBooks' own screen makes is refused or discarded over the API), so the bill's memo names the PO and the PO is closed so it cannot be billed twice. The bill carries the PO's lines. When the vendor's invoice differs from the PO, change the line amounts afterwards with update_bill (QuickBooks computes a bill's total from its lines, so there is no total to override).On Xero this is a read of the order plus a create of the bill - Xero has no convert endpoint - and it then marks the order BILLED so a second call cannot bill the same goods twice. An order already BILLED is refused by name. If the order has no delivery date to borrow, due_date is required, because Xero will not accept a bill without one. Here too the bill carries the order's lines, and update_bill changes their amounts afterwards.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
4 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › purchase_order_id
Id of an open purchase order. Find it with search_purchase_orders.
Clear enough to supply this argument.
params › txn_date
Bill date. Use the vendor invoice date, not today's.
Clear enough to supply this argument.
params › due_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › doc_number
The vendor's invoice number.
Clear enough to supply this argument.
params › private_note
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Convert Purchase Order to Bill",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "convert_purchase_order_to_bill",
"title": "Convert Purchase Order to Bill",
"description": "Convert a purchase order into a bill in QuickBooks Online and close the PO in one step. ALWAYS use this to bill against a PO. A bill created separately with create_bill looks completely correct - the expense posts and the vendor gets paid - but leaves the purchase order open indefinitely with no visible symptom. QuickBooks' API cannot link a bill to a purchase order (the link QuickBooks' own screen makes is refused or discarded over the API), so the bill's memo names the PO and the PO is closed so it cannot be billed twice. The bill carries the PO's lines. When the vendor's invoice differs from the PO, change the line amounts afterwards with update_bill (QuickBooks computes a bill's total from its lines, so there is no total to override).On Xero this is a read of the order plus a create of the bill - Xero has no convert endpoint - and it then marks the order BILLED so a second call cannot bill the same goods twice. An order already BILLED is refused by name. If the order has no delivery date to borrow, due_date is required, because Xero will not accept a bill without one. Here too the bill carries the order's lines, and update_bill changes their amounts afterwards.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"purchase_order_id",
"realm_id"
],
"properties": {
"due_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"txn_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Bill date. Use the vendor invoice date, not today's."
},
"doc_number": {
"type": "string",
"maxLength": 21,
"description": "The vendor's invoice number."
},
"private_note": {
"type": "string",
"maxLength": 4000
},
"purchase_order_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of an open purchase order. Find it with search_purchase_orders."
}
}
}
}
},
"annotations": {
"title": "Convert Purchase Order to Bill",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
Align the title with the capability actually described by this tool.
Description94/100
Void an invoice. On QuickBooks this keeps the document and its number in the books at a zero amount. On Xero a draft or submitted document moves to DELETED and a posted one to VOIDED - both are status transitions, so the record and its number stay retrievable and the audit trail survives either way. There is NO hard delete for invoices through this connector, so when a user asks to delete one, void is the only option: say so rather than reporting that it cannot be done.VOID SERVES ONLY INVOICES AND PAYMENTS. If what you were asked to void is a purchase, expense or credit-card charge, this tool is not it: QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Input documentation gives an agent enough context to populate the arguments.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "void_invoice",
"title": "Void Invoice",
"description": "Void an invoice. On QuickBooks this keeps the document and its number in the books at a zero amount. On Xero a draft or submitted document moves to DELETED and a posted one to VOIDED - both are status transitions, so the record and its number stay retrievable and the audit trail survives either way. There is NO hard delete for invoices through this connector, so when a user asks to delete one, void is the only option: say so rather than reporting that it cannot be done.VOID SERVES ONLY INVOICES AND PAYMENTS. If what you were asked to void is a purchase, expense or credit-card charge, this tool is not it: QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
}
}
}
}
},
"annotations": {
"title": "Void Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Void a payment in QuickBooks Online. Voiding keeps the document and its number in the books at a zero amount, so the audit trail survives - which is what an auditor or CPA expects to find. There is NO delete for payments through this connector, so when a user asks to delete one, void is the only option: say so rather than reporting that it cannot be done.On Xero this is REFUSED rather than routed to a delete, because the two are different instructions: voiding keeps the document at zero so the audit trail survives, and Xero's delete removes it. The refusal names delete_bill_payment and what it costs, so you choose.VOID SERVES ONLY INVOICES AND PAYMENTS. If what you were asked to void is a purchase, expense or credit-card charge, this tool is not it: QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "void_payment",
"title": "Void Payment",
"description": "Void a payment in QuickBooks Online. Voiding keeps the document and its number in the books at a zero amount, so the audit trail survives - which is what an auditor or CPA expects to find. There is NO delete for payments through this connector, so when a user asks to delete one, void is the only option: say so rather than reporting that it cannot be done.On Xero this is REFUSED rather than routed to a delete, because the two are different instructions: voiding keeps the document at zero so the audit trail survives, and Xero's delete removes it. The refusal names delete_bill_payment and what it costs, so you choose.VOID SERVES ONLY INVOICES AND PAYMENTS. If what you were asked to void is a purchase, expense or credit-card charge, this tool is not it: QuickBooks has NO void for a purchase or expense: the API refuses operation=void on a Purchase outright (measured), and void_invoice / void_payment serve only those two document types. There are TWO ways to cancel one and they are not interchangeable - the bookkeeper chooses, so offer the choice rather than picking for them. DELETE it with delete_purchase when the document should never have existed: a duplicate, a row posted twice, an import being undone. Nothing is preserved because there is nothing worth preserving, and a zeroed ghost would sit in every transaction list forever. ZERO it instead - every line to Amount 0.00 via update_purchase - when the transaction was real and is being cancelled: the record and its number stay in the books, which is what an auditor expects to find. QuickBooks accepts 0.00 on both create and update. NEVER use a token amount such as 0.01 to stand in for zero - it leaves a real one-cent expense in the client's books that reads as a genuine transaction and has to be found and removed later. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Void Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Email a invoice to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch here. The one exception is overdue reminders: send_overdue_invoice_reminders sends a list the user approved with one yes. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out.On Xero this is the only email endpoint that exists, and it is customer-invoices-only: bills, quotes, purchase orders and credit notes cannot be emailed by the API and are refused by name. Xero sends to the CONTACT'S OWN address from the organisation's template as the connected user, so it takes no recipient - passing one is refused rather than silently ignored, because an ignored address sends somewhere other than you asked. A DRAFT is refused. If Xero returns a 400 the usual cause is the organisation's plan: API invoice email is not available on Partner Edition, which is what practices commonly put client organisations on. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › id
Id of the invoice to send. Find it with search_invoices.
Clear enough to supply this argument.
params › send_to
Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_invoice_email",
"title": "Send Invoice by Email",
"description": "Email a invoice to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch here. The one exception is overdue reminders: send_overdue_invoice_reminders sends a list the user approved with one yes. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out.On Xero this is the only email endpoint that exists, and it is customer-invoices-only: bills, quotes, purchase orders and credit notes cannot be emailed by the API and are refused by name. Xero sends to the CONTACT'S OWN address from the organisation's template as the connected user, so it takes no recipient - passing one is refused rather than silently ignored, because an ignored address sends somewhere other than you asked. A DRAFT is refused. If Xero returns a 400 the usual cause is the organisation's plan: API invoice email is not available on Partner Edition, which is what practices commonly put client organisations on. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the invoice to send. Find it with search_invoices."
},
"send_to": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 320,
"description": "Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Send Invoice by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Email a estimate to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › id
Id of the estimate to send. Find it with search_estimates.
Clear enough to supply this argument.
params › send_to
Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_estimate_email",
"title": "Send Estimate by Email",
"description": "Email a estimate to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the estimate to send. Find it with search_estimates."
},
"send_to": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 320,
"description": "Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Send Estimate by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Email a purchase order to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › id
Id of the purchase order to send. Find it with search_purchase_orders.
Clear enough to supply this argument.
params › send_to
Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Send Purchase Order by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_purchase_order",
"title": "Send Purchase Order by Email",
"description": "Email a purchase order to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the purchase order to send. Find it with search_purchase_orders."
},
"send_to": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 320,
"description": "Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Send Purchase Order by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Email a sales receipt to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › id
Id of the sales receipt to send. Find it with search_sales_receipts.
Clear enough to supply this argument.
params › send_to
Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_sales_receipt",
"title": "Send Sales Receipt by Email",
"description": "Email a sales receipt to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the sales receipt to send. Find it with search_sales_receipts."
},
"send_to": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 320,
"description": "Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Send Sales Receipt by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Email a credit memo to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › id
Id of the credit memo to send. Find it with search_credit_memos.
Clear enough to supply this argument.
params › send_to
Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_credit_memo",
"title": "Send Credit Memo by Email",
"description": "Email a credit memo to its recipient via QuickBooks Online. QuickBooks sends the mail from the client's own sending identity and template. THIS CANNOT BE UNDONE: the message reaches a third party and no tool can recall it. Off unless the firm has enabled document sending; while it is off this returns send_not_enabled. Always show the user the exact recipient address and get explicit approval before calling this, and send one document per approval - never batch. QuickBooks accepts the send and queues the mail, so do not delete or void the document straight after sending: deleting it stops the mail from ever going out. Xero companies: Xero can only email customer invoices, so this is refused there with a pointer to send it from Xero directly. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the credit memo to send. Find it with search_credit_memos."
},
"send_to": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"maxLength": 320,
"description": "Override the address on file. Prefer omitting this and fixing the customer record instead - a typo here delivers a client's financial document to a stranger. An address not on the document is held until a person confirms it once for this company in NumbersGame."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Send Credit Memo by Email",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
List every overdue customer invoice in a QuickBooks Online or Xero company: open (amount due above zero) and past its due date by any number of days, oldest due first. Each row has the customer, invoice number, amount due, currency, due date, days overdue and the email address the ledger would send a reminder to (null when there is none, so it cannot be emailed). On QuickBooks that is the invoice's own email; on Xero it is the contact's email address, because Xero always mails the contact. On Xero only approved (AUTHORISED) invoices are listed: a draft or one awaiting approval is not owed yet. Days are counted against today's date in UTC. All pages are read, so the list is complete. Use it before send_overdue_invoice_reminders: show the user this whole list, including every email address, and get one explicit yes for the invoices to remind.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_overdue_invoices",
"title": "List Overdue Invoices",
"description": "List every overdue customer invoice in a QuickBooks Online or Xero company: open (amount due above zero) and past its due date by any number of days, oldest due first. Each row has the customer, invoice number, amount due, currency, due date, days overdue and the email address the ledger would send a reminder to (null when there is none, so it cannot be emailed). On QuickBooks that is the invoice's own email; on Xero it is the contact's email address, because Xero always mails the contact. On Xero only approved (AUTHORISED) invoices are listed: a draft or one awaiting approval is not owed yet. Days are counted against today's date in UTC. All pages are read, so the list is complete. Use it before send_overdue_invoice_reminders: show the user this whole list, including every email address, and get one explicit yes for the invoices to remind.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "List Overdue Invoices",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Email overdue-invoice reminders for a list of QuickBooks Online or Xero invoices the user approved, in one call. Each invoice is re-sent by the ledger itself, from the client's own sending identity and template - the same send as send_invoice_email: QuickBooks mails the address on the invoice, Xero mails the contact's own email address. THIS CANNOT BE UNDONE: every message reaches a third party. One approval covers the whole list, and only this list: first call list_overdue_invoices and show the user every invoice you intend to remind with its customer, invoice number, amount due, days overdue and email address; pass only the ids the user said yes to, and ask again for anything added. At most 50 invoices per call; for more, send the first 50 and then the rest in another call. Returns one result per invoice: sent, refused (with the code and reason; a refused invoice does not stop the others) or failed (the ledger's error; on Xero a 400 usually means the organisation's plan, e.g. Partner Edition, has no API invoice email). Off unless the firm has enabled document sending (send_not_enabled, nothing sent). Do not delete or void a reminded invoice straight after: deleting it stops the queued mail. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › invoice_ids
Ids of the overdue invoices the user approved, from list_overdue_invoices.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "send_overdue_invoice_reminders",
"title": "Send Overdue Invoice Reminders",
"description": "Email overdue-invoice reminders for a list of QuickBooks Online or Xero invoices the user approved, in one call. Each invoice is re-sent by the ledger itself, from the client's own sending identity and template - the same send as send_invoice_email: QuickBooks mails the address on the invoice, Xero mails the contact's own email address. THIS CANNOT BE UNDONE: every message reaches a third party. One approval covers the whole list, and only this list: first call list_overdue_invoices and show the user every invoice you intend to remind with its customer, invoice number, amount due, days overdue and email address; pass only the ids the user said yes to, and ask again for anything added. At most 50 invoices per call; for more, send the first 50 and then the rest in another call. Returns one result per invoice: sent, refused (with the code and reason; a refused invoice does not stop the others) or failed (the ledger's error; on Xero a 400 usually means the organisation's plan, e.g. Partner Edition, has no API invoice email). Off unless the firm has enabled document sending (send_not_enabled, nothing sent). Do not delete or void a reminded invoice straight after: deleting it stops the queued mail. Held with recipient_unconfirmed, and nothing sent, while the document's customer or vendor has an email set or changed through NumbersGame that no person has confirmed, or while send_to is neither on the document nor confirmed for this company. A person confirms in NumbersGame (Firm settings → Document sending → Recipients) with a password or passkey; then call the send again. No parameter skips this.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice_ids",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"invoice_ids": {
"type": "array",
"items": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"maxItems": 50,
"minItems": 1,
"description": "Ids of the overdue invoices the user approved, from list_overdue_invoices."
}
}
}
}
},
"annotations": {
"title": "Send Overdue Invoice Reminders",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
List the files already attached to a QuickBooks Online transaction: receipts, contracts, statements, supporting memos. Call this BEFORE offering to attach a supporting memo, so a close that runs twice does not leave two memos saying the same thing. Also the fastest way to answer an auditor or CPA asking whether a journal entry was ever documented.On Xero, attachments hang off the document at {Endpoint}/{id}/Attachments. Pass the QuickBooks entity type you mean - Invoice, Bill, Purchase, JournalEntry, CreditMemo, Customer or Vendor - and it is mapped to the Xero endpoint (Bill and Invoice are the same one there, Purchase is a BankTransaction, JournalEntry is a ManualJournal). A type Xero has no attachment endpoint for is refused with the list rather than producing a 404 from a guessed path. For several, make the calls one at a time, not in parallel: QuickBooks rate-limits a parallel burst (code 3001).
Describe the returned information so the agent knows whether it will answer the request.
Inputs83/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › entity_type
QBO entity type the attachment is linked to, e.g. Purchase, Bill, Invoice, JournalEntry.
Clear enough to supply this argument.
params › entity_id
Id of that transaction.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_attachments",
"title": "List Attachments",
"description": "List the files already attached to a QuickBooks Online transaction: receipts, contracts, statements, supporting memos. Call this BEFORE offering to attach a supporting memo, so a close that runs twice does not leave two memos saying the same thing. Also the fastest way to answer an auditor or CPA asking whether a journal entry was ever documented.On Xero, attachments hang off the document at {Endpoint}/{id}/Attachments. Pass the QuickBooks entity type you mean - Invoice, Bill, Purchase, JournalEntry, CreditMemo, Customer or Vendor - and it is mapped to the Xero endpoint (Bill and Invoice are the same one there, Purchase is a BankTransaction, JournalEntry is a ManualJournal). A type Xero has no attachment endpoint for is refused with the list rather than producing a 404 from a guessed path. For several, make the calls one at a time, not in parallel: QuickBooks rate-limits a parallel burst (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entity_type",
"entity_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of that transaction."
},
"entity_type": {
"type": "string",
"maxLength": 40,
"description": "QBO entity type the attachment is linked to, e.g. Purchase, Bill, Invoice, JournalEntry."
}
}
}
}
},
"annotations": {
"title": "List Attachments",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Record billable or payroll hours against an employee or vendor in QuickBooks Online, optionally against a customer so the time can be billed on. Find one afterwards with search_time_activities and correct it with update_time_activity. There is no DELETE for time activities, and they do not appear in the transaction list or general ledger, so search_time_activities is the only way to see one again. Read the fields back before posting anyway - hours and dates are easy to mistype and easy to miss later. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.
The description explains the capability, when to use it, and what to expect.
Inputs19/100
3 of 16 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › time_activity › NameOf
Whether the time is an employee's or a vendor's.
Clear enough to supply this argument.
params › time_activity › EmployeeRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › EmployeeRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › TxnDate
The date the work was done, not today. Correctable afterwards with update_time_activity.
Clear enough to supply this argument.
params › time_activity › Hours
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › Minutes
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › ItemRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › ItemRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › BillableStatus
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › HourlyRate
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_time_activity",
"title": "Log Time Activity",
"description": "Record billable or payroll hours against an employee or vendor in QuickBooks Online, optionally against a customer so the time can be billed on. Find one afterwards with search_time_activities and correct it with update_time_activity. There is no DELETE for time activities, and they do not appear in the transaction list or general ledger, so search_time_activities is the only way to see one again. Read the fields back before posting anyway - hours and dates are easy to mistype and easy to miss later. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"time_activity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"time_activity": {
"type": "object",
"required": [
"NameOf",
"TxnDate"
],
"properties": {
"Hours": {
"type": "integer",
"maximum": 999,
"minimum": 0
},
"NameOf": {
"enum": [
"Employee",
"Vendor"
],
"type": "string",
"description": "Whether the time is an employee's or a vendor's."
},
"ItemRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Service item, required for billable time."
},
"Minutes": {
"type": "integer",
"maximum": 59,
"minimum": 0
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The date the work was done, not today. Correctable afterwards with update_time_activity."
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Required when NameOf is Vendor. Look up with search_vendors."
},
"HourlyRate": {
"type": "number",
"maximum": 999999.99,
"minimum": 0
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer the time is for, if it is being billed on."
},
"Description": {
"type": "string",
"maxLength": 4000
},
"EmployeeRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Required when NameOf is Employee. Look up with search_employees."
},
"BillableStatus": {
"enum": [
"Billable",
"NotBillable",
"HasBeenBilled"
],
"type": "string"
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Log Time Activity",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Post many bank statement rows into QuickBooks Online or Xero in one call, as Purchases (money out) and Deposits (money in). This is the bank CSV import path: for an uploaded or exported statement, on an account with or without a bank feed. A row that matches a bank-feed line not yet booked is NOT refused: it posts, and its entry then claims that line, so the feed will not post the same money again; the result names the line per row (`feed_claim`) and how to release a wrong match (reverse_bank_booking, which frees the line and leaves the entry), a dry run names the line each row would claim and claims nothing, and reverse_csv_import releases the claims with the entries it removes. You parse the CSV in the conversation and send structured rows; the file never reaches our servers. Rows matching transactions already on the account in the same date range are refused as duplicates and reported back. If the file covers a wider span than the statement - a full calendar-month export for a card statement that runs mid-month to mid-month - pass start_date and end_date: rows outside that period are excluded from the import and reported back, and the statement_totals check then applies to the rows inside it. Always run with dry_run true first: besides duplicates, the dry run checks every row with the same coding engine the bank feed uses - the company's bank rules, the open bills a payment would settle, capital purchases, payroll, and the rest - and reports per row a score, the reasons to look at it (`engine.vetoes`) and the account the company's rule names when it is not the one you chose; show the user those rows and fix what they agree with before posting. A flagged row posts only once the user has answered it: pass vetoes_reviewed (their answer for the import) and, where the dry run says a row needs its own answer, veto_reason on that row. An unanswered flagged row is HELD - kept with the import, not posted, and resolved later with resolve_statement_lines - and the score never holds a row. Posting requires statement_totals - the opening balance, closing balance and row count from the statement, which you must ask the user for; the server checks the rows reconcile to them and refuses to post if they do not. A transaction export (a card platform such as Ramp or Brex, an expense tool) is not a statement and prints no balances: ask for the statement's own figures, never work them out from the rows, or the check proves nothing. Use the same date column every month - the transaction date, not a settlement or posted date - so no row moves across a period edge. If some rows fail, never resend the file or just the failed rows here (the first double-posts, the second cannot reconcile): fix each and post it with create_deposit or create_purchase. On Xero, the duplicate check also needs the account's register to tie to Xero's own bank summary; Xero hides Receipts and Expense Claims from this connection, so an account holding one may not tie. A dry run then warns with the difference, and a post is refused unless you import month by month or pass register_incomplete_reason after the user has checked that difference in Xero. Returns an import run id which reverse_csv_import can undo in one step. A post waits up to 45 seconds for its rows; a larger import (on Xero, about a second a row) keeps posting after the call returns, and the result then says status "posting" with the run id: call get_csv_import_run with it until status is complete, and never send the file again meanwhile - a second import onto the same account is refused while one is posting.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
21 of 25 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › account_id
QBO bank or credit card account the statement belongs to.
Clear enough to supply this argument.
params › account_name
That account's name, used for the duplicate scan.
Clear enough to supply this argument.
params › rows › items › row_index
Position in the file. Defaults to array order.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › rows › items › type
Purchase for money out, Deposit for money in. A statement row is never a journal entry. On a credit card a refund is a Deposit. A card REPAYMENT is usually already booked from the bank account it was paid from, and importing it here too counts it twice: show repayments to the user and check the bank side before sending any.
Clear enough to supply this argument.
params › rows › items › txn_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › rows › items › amount
Amount, sign ignored - direction comes from type.
Clear enough to supply this argument.
params › rows › items › description
The bank's own description for this row, VERBATIM from the file. Do not tidy it, expand an abbreviation, or replace it with what you worked out the transaction was - a bookkeeper reconciling against the statement matches on this exact string, and an auditor expects to find it. Put anything you worked out in `memo` instead. When the file splits the description over several columns - a card platform export (Ramp, Brex, an expense tool) has separate merchant, category and cardholder columns - this is the MERCHANT column alone, verbatim; the category, cardholder and the rest go in `memo`. Never join columns here: the company's rules and its posting history match on this exact string, so `Anthropic - SaaS - J. Smith` is a different vendor from `Anthropic`, and from the same merchant on another cardholder.
Clear enough to supply this argument.
params › rows › items › memo
A note ABOUT this row - what you determined, or why it is coded the way it is. Optional. It is appended after the bank's description in the QuickBooks memo (Xero: Reference); it never replaces it.
Clear enough to supply this argument.
params › rows › items › category_account_id
Income or expense account this row is coded to. NOT the bank account.
Clear enough to supply this argument.
params › rows › items › veto_reason
The user's answer to THIS row's flags from the dry run (`engine.vetoes`), in their words, e.g. "capital purchase - it is a laptop under our policy, expense it". Needed only where the dry run said the row needs its own answer (`needs: its_own_answer`: a capital purchase, or a payment with no open bill under strict bill matching); everything else is answered for the whole import by vetoes_reviewed.
Clear enough to supply this argument.
params › rows › items › entity_id
Vendor or customer. Look up with search_vendors / search_customers.
Clear enough to supply this argument.
params › rows › items › entity_type
Not provided
Missing description. Explain what this value means and how to supply it.
params › rows › items › class_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › rows › items › department_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › not_a_bank_line
Only when these rows are NOT the bank-feed lines they match - for example a period the feed covers but books separately. Give the reason; it is recorded. Without it a row that matches an unbooked feed line posts and claims that line; with it the row posts and the line is left for the feed, so the same money can be posted twice. Never needed just because the account has a feed.
Clear enough to supply this argument.
params › register_incomplete_reason
Xero only, and only when a dry run or a refusal said this account's register is incomplete for the period (its readable transactions do not tie to Xero's bank summary). Say what the user checked in Xero - that the stated difference is not any of these rows. It is recorded. The rows are still checked against every transaction we can read; this accepts only the unseen difference. Never send it pre-emptively.
Clear enough to supply this argument.
params › dry_run
True validates and reports the plan without posting. Always do this first.
Clear enough to supply this argument.
params › vetoes_reviewed
The user's answer to the flagged rows the dry run showed, for the whole import, e.g. "reviewed the preview with the user; post as shown". Send it only after showing the user the rows the dry run flagged. Without it every flagged row is HELD rather than posted; with it, flagged rows post with this answer recorded, except a row that needs its own answer (veto_reason) or a fix. Rows with no flag post either way.
Clear enough to supply this argument.
params › start_date
First day of the statement period, inclusive. Giving either bound SCOPES the import: rows outside the period are excluded rather than posted, and statement_totals is checked against the rows inside it. Omit both and every row is imported, with the period taken as the span of the rows themselves.
Clear enough to supply this argument.
params › end_date
Last day of the statement period, inclusive. See start_date - giving either bound scopes the import.
Clear enough to supply this argument.
params › allow_duplicate_rows
row_index values to post despite matching an existing transaction. Use ONE ROW AT A TIME after the user confirms each; never pass the whole set to force a file through.
Clear enough to supply this argument.
params › statement_totals › opening_balance
Opening balance printed on the statement. Exactly as printed - on a credit card that is the balance OWED at the start of the period, not a negative number.
Clear enough to supply this argument.
params › statement_totals › closing_balance
Closing balance printed on the statement. Exactly as printed. Never swap this with the opening balance to make the check pass: the server knows whether the account is a bank or a card and reconciles in the right direction for each.
Clear enough to supply this argument.
params › statement_totals › row_count
How many transaction rows the statement has.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "bulk_create_transactions",
"title": "Import Bank Transactions",
"description": "Post many bank statement rows into QuickBooks Online or Xero in one call, as Purchases (money out) and Deposits (money in). This is the bank CSV import path: for an uploaded or exported statement, on an account with or without a bank feed. A row that matches a bank-feed line not yet booked is NOT refused: it posts, and its entry then claims that line, so the feed will not post the same money again; the result names the line per row (`feed_claim`) and how to release a wrong match (reverse_bank_booking, which frees the line and leaves the entry), a dry run names the line each row would claim and claims nothing, and reverse_csv_import releases the claims with the entries it removes. You parse the CSV in the conversation and send structured rows; the file never reaches our servers. Rows matching transactions already on the account in the same date range are refused as duplicates and reported back. If the file covers a wider span than the statement - a full calendar-month export for a card statement that runs mid-month to mid-month - pass start_date and end_date: rows outside that period are excluded from the import and reported back, and the statement_totals check then applies to the rows inside it. Always run with dry_run true first: besides duplicates, the dry run checks every row with the same coding engine the bank feed uses - the company's bank rules, the open bills a payment would settle, capital purchases, payroll, and the rest - and reports per row a score, the reasons to look at it (`engine.vetoes`) and the account the company's rule names when it is not the one you chose; show the user those rows and fix what they agree with before posting. A flagged row posts only once the user has answered it: pass vetoes_reviewed (their answer for the import) and, where the dry run says a row needs its own answer, veto_reason on that row. An unanswered flagged row is HELD - kept with the import, not posted, and resolved later with resolve_statement_lines - and the score never holds a row. Posting requires statement_totals - the opening balance, closing balance and row count from the statement, which you must ask the user for; the server checks the rows reconcile to them and refuses to post if they do not. A transaction export (a card platform such as Ramp or Brex, an expense tool) is not a statement and prints no balances: ask for the statement's own figures, never work them out from the rows, or the check proves nothing. Use the same date column every month - the transaction date, not a settlement or posted date - so no row moves across a period edge. If some rows fail, never resend the file or just the failed rows here (the first double-posts, the second cannot reconcile): fix each and post it with create_deposit or create_purchase. On Xero, the duplicate check also needs the account's register to tie to Xero's own bank summary; Xero hides Receipts and Expense Claims from this connection, so an account holding one may not tie. A dry run then warns with the difference, and a post is refused unless you import month by month or pass register_incomplete_reason after the user has checked that difference in Xero. Returns an import run id which reverse_csv_import can undo in one step. A post waits up to 45 seconds for its rows; a larger import (on Xero, about a second a row) keeps posting after the call returns, and the result then says status \"posting\" with the run id: call get_csv_import_run with it until status is complete, and never send the file again meanwhile - a second import onto the same account is refused while one is posting.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"account_id",
"account_name",
"rows",
"realm_id"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object",
"required": [
"type",
"txn_date",
"amount",
"category_account_id"
],
"properties": {
"memo": {
"type": "string",
"maxLength": 4000,
"description": "A note ABOUT this row - what you determined, or why it is coded the way it is. Optional. It is appended after the bank's description in the QuickBooks memo (Xero: Reference); it never replaces it."
},
"type": {
"enum": [
"Purchase",
"Deposit"
],
"type": "string",
"description": "Purchase for money out, Deposit for money in. A statement row is never a journal entry. On a credit card a refund is a Deposit. A card REPAYMENT is usually already booked from the bank account it was paid from, and importing it here too counts it twice: show repayments to the user and check the bank side before sending any."
},
"amount": {
"type": "number",
"maximum": 999999999.99,
"description": "Amount, sign ignored - direction comes from type."
},
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"txn_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Vendor or customer. Look up with search_vendors / search_customers."
},
"row_index": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Position in the file. Defaults to array order."
},
"description": {
"type": "string",
"maxLength": 4000,
"description": "The bank's own description for this row, VERBATIM from the file. Do not tidy it, expand an abbreviation, or replace it with what you worked out the transaction was - a bookkeeper reconciling against the statement matches on this exact string, and an auditor expects to find it. Put anything you worked out in `memo` instead. When the file splits the description over several columns - a card platform export (Ramp, Brex, an expense tool) has separate merchant, category and cardholder columns - this is the MERCHANT column alone, verbatim; the category, cardholder and the rest go in `memo`. Never join columns here: the company's rules and its posting history match on this exact string, so `Anthropic - SaaS - J. Smith` is a different vendor from `Anthropic`, and from the same merchant on another cardholder."
},
"entity_type": {
"enum": [
"Vendor",
"Customer",
"Employee"
],
"type": "string"
},
"veto_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "The user's answer to THIS row's flags from the dry run (`engine.vetoes`), in their words, e.g. \"capital purchase - it is a laptop under our policy, expense it\". Needed only where the dry run said the row needs its own answer (`needs: its_own_answer`: a capital purchase, or a payment with no open bill under strict bill matching); everything else is answered for the whole import by vetoes_reviewed."
},
"department_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"category_account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Income or expense account this row is coded to. NOT the bank account."
}
}
},
"maxItems": 500,
"minItems": 1,
"description": "One entry per statement row."
},
"dry_run": {
"type": "boolean",
"description": "True validates and reports the plan without posting. Always do this first."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day of the statement period, inclusive. See start_date - giving either bound scopes the import."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO bank or credit card account the statement belongs to."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day of the statement period, inclusive. Giving either bound SCOPES the import: rows outside the period are excluded rather than posted, and statement_totals is checked against the rows inside it. Omit both and every row is imported, with the period taken as the span of the rows themselves."
},
"account_name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "That account's name, used for the duplicate scan."
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when these rows are NOT the bank-feed lines they match - for example a period the feed covers but books separately. Give the reason; it is recorded. Without it a row that matches an unbooked feed line posts and claims that line; with it the row posts and the line is left for the feed, so the same money can be posted twice. Never needed just because the account has a feed."
},
"vetoes_reviewed": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "The user's answer to the flagged rows the dry run showed, for the whole import, e.g. \"reviewed the preview with the user; post as shown\". Send it only after showing the user the rows the dry run flagged. Without it every flagged row is HELD rather than posted; with it, flagged rows post with this answer recorded, except a row that needs its own answer (veto_reason) or a fix. Rows with no flag post either way."
},
"statement_totals": {
"type": "object",
"required": [
"opening_balance",
"closing_balance",
"row_count"
],
"properties": {
"row_count": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "How many transaction rows the statement has."
},
"closing_balance": {
"type": "number",
"description": "Closing balance printed on the statement. Exactly as printed. Never swap this with the opening balance to make the check pass: the server knows whether the account is a bank or a card and reconciles in the right direction for each."
},
"opening_balance": {
"type": "number",
"description": "Opening balance printed on the statement. Exactly as printed - on a credit card that is the balance OWED at the start of the period, not a negative number."
}
},
"description": "REQUIRED TO POST. Ask the user for these three figures from the statement itself before posting - do not read them off the file you parsed, the whole point is to check the file against something independent. The server verifies that the rows account for the movement between the two balances and that the count matches, and refuses to post if they do not. It reconciles in the direction the account requires - a bank balance rises with deposits, a credit card balance rises with charges - so give both balances as the statement prints them and do not reverse them to clear the check. A dry run does not need them."
},
"allow_duplicate_rows": {
"type": "array",
"items": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"maxItems": 500,
"description": "row_index values to post despite matching an existing transaction. Use ONE ROW AT A TIME after the user confirms each; never pass the whole set to force a file through."
},
"register_incomplete_reason": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Xero only, and only when a dry run or a refusal said this account's register is incomplete for the period (its readable transactions do not tie to Xero's bank summary). Say what the user checked in Xero - that the stated difference is not any of these rows. It is recorded. The rows are still checked against every transaction we can read; this accepts only the unseen difference. Never send it pre-emptively."
}
}
}
}
},
"annotations": {
"title": "Import Bank Transactions",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Undo an entire bank CSV import by its run id, deleting every transaction that run posted into QuickBooks Online or Xero. The whole run comes out in one call, however many rows it posted. A row that had claimed a bank-feed line releases it as its entry is removed, so the line goes back to the feed's review queue; nothing the import did not post is deleted (a feed booking of the same money stays). Safe to run twice: a run already reversed is a no-op.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Input documentation gives an agent enough context to populate the arguments.
params › run_id
The import run id reported when the CSV was imported.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "reverse_csv_import",
"title": "Reverse Bank Import",
"description": "Undo an entire bank CSV import by its run id, deleting every transaction that run posted into QuickBooks Online or Xero. The whole run comes out in one call, however many rows it posted. A row that had claimed a bank-feed line releases it as its entry is removed, so the line goes back to the feed's review queue; nothing the import did not post is deleted (a feed booking of the same money stays). Safe to run twice: a run already reversed is a no-op.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"realm_id"
],
"properties": {
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The import run id reported when the CSV was imported."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Reverse Bank Import",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Read-only. The progress and result of a bank statement import (bulk_create_transactions) by its run id. A post waits up to 45 seconds and then, for a larger import (on Xero about a second a row), returns status "posting" while it keeps posting; call this with that run_id until status is "complete" and report the result it gives. While it is posting the answer is progress only (counts, and check_again_in_seconds: wait that long before the next call); the rows come once it has finished, which is the same result the import gives when it finishes in time: rows posted with their ids (and, for a row that matched a bank-feed line not yet booked, `feed_claim`: the line it claimed, a POSSIBLE DUPLICATE naming both entries when another entry had it first, or why it could not be claimed), refused as duplicates, failed with the ledger's reason, held for review, and outside the period. Status "interrupted" means the import stopped early (a server restart, a ledger call that did not answer in time, or an unexpected error): the rows it had not posted are held with the reason; resolve_statement_lines posts a never-sent row after re-reading the register, and holds back a row that was being sent for 15 minutes, until that call cannot still land. Never send the file again, while it posts or after: every row it did not post ends held or failed, each with its own route. Works the same for a company on QuickBooks Online or on Xero: this reads NumbersGame's own import records.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › run_id
The import run id bulk_create_transactions returned.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_csv_import_run",
"title": "Get Statement Import Run",
"description": "Read-only. The progress and result of a bank statement import (bulk_create_transactions) by its run id. A post waits up to 45 seconds and then, for a larger import (on Xero about a second a row), returns status \"posting\" while it keeps posting; call this with that run_id until status is \"complete\" and report the result it gives. While it is posting the answer is progress only (counts, and check_again_in_seconds: wait that long before the next call); the rows come once it has finished, which is the same result the import gives when it finishes in time: rows posted with their ids (and, for a row that matched a bank-feed line not yet booked, `feed_claim`: the line it claimed, a POSSIBLE DUPLICATE naming both entries when another entry had it first, or why it could not be claimed), refused as duplicates, failed with the ledger's reason, held for review, and outside the period. Status \"interrupted\" means the import stopped early (a server restart, a ledger call that did not answer in time, or an unexpected error): the rows it had not posted are held with the reason; resolve_statement_lines posts a never-sent row after re-reading the register, and holds back a row that was being sent for 15 minutes, until that call cannot still land. Never send the file again, while it posts or after: every row it did not post ends held or failed, each with its own route. Works the same for a company on QuickBooks Online or on Xero: this reads NumbersGame's own import records.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"realm_id"
],
"properties": {
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The import run id bulk_create_transactions returned."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Statement Import Run",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Read-only. The bank statement lines a CSV or pasted import HELD instead of posting, because the coding check flagged them and the user had not answered yet (a capital purchase, a payment that should settle an open bill, a first-time vendor, a rule naming another account, and so on). They are on the statement and not yet in the books, and they stay held until resolved, across conversations. Grouped per import (account and period), each line re-checked now with its flags, the reasons in words, and what clears it: `an_answer` (the user's go-ahead), `its_own_answer` (a sentence about that line), `a_fix` (recode or dismiss), or `nothing` (a setting changed since and it would post as it is). Call this at the start of any statement or bank session for the company. Resolve lines with resolve_statement_lines. Works the same for a company on QuickBooks Online or on Xero: this reads NumbersGame's own import records.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › limit
Most lines to return, newest import first. Default 200.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_held_statement_lines",
"title": "List Held Statement Lines",
"description": "Read-only. The bank statement lines a CSV or pasted import HELD instead of posting, because the coding check flagged them and the user had not answered yet (a capital purchase, a payment that should settle an open bill, a first-time vendor, a rule naming another account, and so on). They are on the statement and not yet in the books, and they stay held until resolved, across conversations. Grouped per import (account and period), each line re-checked now with its flags, the reasons in words, and what clears it: `an_answer` (the user's go-ahead), `its_own_answer` (a sentence about that line), `a_fix` (recode or dismiss), or `nothing` (a setting changed since and it would post as it is). Call this at the start of any statement or bank session for the company. Resolve lines with resolve_statement_lines. Works the same for a company on QuickBooks Online or on Xero: this reads NumbersGame's own import records.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "Most lines to return, newest import first. Default 200."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Held Statement Lines",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Post, recode or dismiss bank statement lines that an import held (list_held_statement_lines shows them), many in one call. Each approved line is checked again before it posts: the coding check runs on it as it is now (with any recode), it posts only once the user has answered its flags (`reason`, and for a line that needs its own answer a sentence about that line), and the account's register is re-read so a line somebody has since entered by hand is not posted twice. Approved lines join their import run, so reverse_csv_import undoes them with it. An approved line that matches a bank-feed line not yet booked claims it once posted, as its import would have (`feed_claim` names the line; reverse_bank_booking releases a wrong match). Dismiss a line that should not post (for example, already entered by hand); the reason is recorded. Only resolve what the user decided. Works the same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
12 of 13 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › decisions › items › run_id
The import run, from list_held_statement_lines.
Clear enough to supply this argument.
params › decisions › items › row_index
The line's row_index in that import.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › decisions › items › action
approve posts the line (with any recode fields below); dismiss lets it go without posting, with a reason.
Clear enough to supply this argument.
params › decisions › items › category_account_id
Recode: post to this income or expense account instead.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › decisions › items › entity_id
Recode: the vendor or customer.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › decisions › items › entity_type
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › class_id
Recode: the class.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › decisions › items › department_id
Recode: the department or location.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › decisions › items › memo
Recode: a note about the line, appended after the bank's description.
Clear enough to supply this argument.
params › decisions › items › reason
The user's answer for this line, in their words. Required to dismiss, and for a line whose flag needs its own answer (needs: its_own_answer, 10+ characters); otherwise the batch `reason` serves.
Clear enough to supply this argument.
params › decisions › items › allow_duplicate
Only after the user confirmed a line reported as possibly already in the books is different money. Never set it pre-emptively.
Clear enough to supply this argument.
params › reason
The user's answer for every line in this call that does not carry its own, e.g. "reviewed with the user; post as shown". Without any answer, a flagged line stays held.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "resolve_statement_lines",
"title": "Resolve Held Statement Lines",
"description": "Post, recode or dismiss bank statement lines that an import held (list_held_statement_lines shows them), many in one call. Each approved line is checked again before it posts: the coding check runs on it as it is now (with any recode), it posts only once the user has answered its flags (`reason`, and for a line that needs its own answer a sentence about that line), and the account's register is re-read so a line somebody has since entered by hand is not posted twice. Approved lines join their import run, so reverse_csv_import undoes them with it. An approved line that matches a bank-feed line not yet booked claims it once posted, as its import would have (`feed_claim` names the line; reverse_bank_booking releases a wrong match). Dismiss a line that should not post (for example, already entered by hand); the reason is recorded. Only resolve what the user decided. Works the same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"decisions",
"realm_id"
],
"properties": {
"reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "The user's answer for every line in this call that does not carry its own, e.g. \"reviewed with the user; post as shown\". Without any answer, a flagged line stays held."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"decisions": {
"type": "array",
"items": {
"type": "object",
"required": [
"run_id",
"row_index",
"action"
],
"properties": {
"memo": {
"type": "string",
"maxLength": 4000,
"description": "Recode: a note about the line, appended after the bank's description."
},
"action": {
"enum": [
"approve",
"dismiss"
],
"type": "string",
"description": "approve posts the line (with any recode fields below); dismiss lets it go without posting, with a reason."
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "The user's answer for this line, in their words. Required to dismiss, and for a line whose flag needs its own answer (needs: its_own_answer, 10+ characters); otherwise the batch `reason` serves."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The import run, from list_held_statement_lines."
},
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Recode: the class."
},
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Recode: the vendor or customer."
},
"row_index": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "The line's row_index in that import."
},
"entity_type": {
"enum": [
"Vendor",
"Customer",
"Employee"
],
"type": "string"
},
"department_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Recode: the department or location."
},
"allow_duplicate": {
"type": "boolean",
"description": "Only after the user confirmed a line reported as possibly already in the books is different money. Never set it pre-emptively."
},
"category_account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Recode: post to this income or expense account instead."
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1,
"description": "One entry per held line; many in one call."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Resolve Held Statement Lines",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a vendor credit in QuickBooks Online. Use when a VENDOR owes the client money back: return to supplier, overbilling, rebate. Does NOT offset the bill by itself: call apply_vendor_credit afterwards or both documents stay open in AP aging. Do NOT use a journal entry or a negative line bill for this, neither shows in AP aging as a credit.On Xero this writes a CreditNote of type ACCPAYCREDIT - the supplier side of the endpoint credit memos use. Lines follow the BILL rules: each needs an account, and Qty and UnitPrice travel together or neither. Measured: Xero does NOT auto-number a supplier credit note - the number belongs to the supplier - so it comes back blank unless you send DocNumber. The note itself is real and its RemainingCredit is set.
The description explains the capability, when to use it, and what to expect.
Inputs13/100
2 of 14 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › vendor_credit › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › Line
At least one line item required
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › vendor_credit › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_vendor_credit",
"title": "Create Vendor Credit",
"description": "Create a vendor credit in QuickBooks Online. Use when a VENDOR owes the client money back: return to supplier, overbilling, rebate. Does NOT offset the bill by itself: call apply_vendor_credit afterwards or both documents stay open in AP aging. Do NOT use a journal entry or a negative line bill for this, neither shows in AP aging as a credit.On Xero this writes a CreditNote of type ACCPAYCREDIT - the supplier side of the endpoint credit memos use. Lines follow the BILL rules: each needs an account, and Qty and UnitPrice travel together or neither. Measured: Xero does NOT auto-number a supplier credit note - the number belongs to the supplier - so it comes back blank unless you send DocNumber. The note itself is real and its RemainingCredit is set.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor_credit",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"vendor_credit": {
"type": "object",
"required": [
"VendorRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Vendor issuing the credit. Look up with search_vendors first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Create Vendor Credit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get a vendor credit by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_vendor_credit and delete_vendor_credit both require.On Xero this reads one supplier CreditNote. A customer credit note id is refused by name rather than returned. For several vendor credits, use one search_vendor_credits call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_vendor_credit calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_vendor_credit",
"title": "Get Vendor Credit",
"description": "Get a vendor credit by Id from QuickBooks Online. Returns the full document including its SyncToken, which update_vendor_credit and delete_vendor_credit both require.On Xero this reads one supplier CreditNote. A customer credit note id is refused by name rather than returned. For several vendor credits, use one search_vendor_credits call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_vendor_credit calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Vendor Credit",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Update a vendor credit in QuickBooks Online. Requires Id and a current SyncToken from get_vendor_credit. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the supplier CreditNote. A customer credit note id is refused by name rather than rewriting the wrong document.
The description explains the capability, when to use it, and what to expect.
Inputs20/100
4 of 16 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › vendor_credit › Id
QBO VendorCredit ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › vendor_credit › SyncToken
Optimistic concurrency token from get_vendor_credit
Clear enough to supply this argument.
params › vendor_credit › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › Line
Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › vendor_credit › APAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › APAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › ClassRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › ClassRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DepartmentRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › DepartmentRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › vendor_credit › TotalAmt
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_vendor_credit",
"title": "Update Vendor Credit",
"description": "Update a vendor credit in QuickBooks Online. Requires Id and a current SyncToken from get_vendor_credit. QuickBooks replaces the whole document, so send every field you want to keep, not just the ones you are changing.On Xero this updates the supplier CreditNote. A customer credit note id is refused by name rather than rewriting the wrong document.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor_credit",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"vendor_credit": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO VendorCredit ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Full replacement line set. QuickBooks replaces all lines, so omit this only if you intend to keep the existing ones untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"ClassRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"TotalAmt": {
"type": "number"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_vendor_credit"
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Vendor issuing the credit. Look up with search_vendors first."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"APAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
},
"DepartmentRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
}
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Update Vendor Credit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description73/100
Delete a vendor credit in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero a credit note is transitioned to DELETED or VOIDED depending on its status. A customer credit note id is refused by name.
Resolve contradictions between the description, input schema, and annotations.
Inputs89/100
Input documentation gives an agent enough context to populate the arguments.
params › idOrEntity
The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with "Required parameter SyncToken is missing in the request" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_vendor_credit",
"title": "Delete Vendor Credit",
"description": "Delete a vendor credit in QuickBooks Online. This REMOVES the record entirely; the document number goes with it. There is no void for this document type through this connector, so if the intent is to cancel while keeping the audit trail, that has to be done in the QuickBooks UI.On Xero a credit note is transitioned to DELETED or VOIDED depending on its status. A customer credit note id is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"idOrEntity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"idOrEntity": {
"description": "The record's QuickBooks Id, as a string -- THE SUPPORTED FORM, and all this needs: the id alone is read back first, so the current SyncToken is supplied for you. You may instead pass the whole object as a search tool returned it, in which case it is posted exactly as given and MUST carry its own Id AND SyncToken -- an object missing SyncToken is refused with \"Required parameter SyncToken is missing in the request\" (code 2020). Pass the object only when you mean to delete against a token you have pinned deliberately; otherwise pass the id."
}
}
}
}
},
"annotations": {
"title": "Delete Vendor Credit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Search vendor credits in QuickBooks Online that match given criteria. Use this to find an existing vendor credit before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads CreditNotes filtered to ACCPAYCREDIT, the supplier side of the same endpoint search_credit_memos reads. Filter on Id, DocNumber, TxnDate, TotalAmt or Balance (RemainingCredit).
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online VendorCredit entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, PrivateNote, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online VendorCredit entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, PrivateNote, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_vendor_credits",
"title": "Search Vendor Credits",
"description": "Search vendor credits in QuickBooks Online that match given criteria. Use this to find an existing vendor credit before creating one, to check for duplicates, or to get an Id and SyncToken for update or delete.On Xero this reads CreditNotes filtered to ACCPAYCREDIT, the supplier side of the same endpoint search_credit_memos reads. Filter on Id, DocNumber, TxnDate, TotalAmt or Balance (RemainingCredit).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online VendorCredit entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, PrivateNote, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online VendorCredit entity. One of: Id, TxnDate, TotalAmt, VendorRef, DocNumber, PrivateNote, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Vendor Credits",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Apply an existing vendor credit against one or more open bills in QuickBooks Online. This is the SECOND HALF of every vendor credit: QuickBooks does not offset a bill with a vendor credit by itself, so a credit recorded and not applied leaves both documents open in AP aging and the vendor balance uncorrected. Call this immediately after create_vendor_credit, in the same approval. Reports the credit's remaining balance afterwards so you can confirm the offset actually landed.On Xero this allocates the supplier credit against a bill. ONE bill per call: Xero's array writes are not all-or-nothing, so a multi-bill allocation that failed partway would spend part of the credit and still report an error. Applying it to a customer invoice is refused by name. txn_date, private_note and bank_account_id have no Xero equivalent - an allocation is dated today and simply offsets the bill - and are refused rather than dropped.
The description explains the capability, when to use it, and what to expect.
Inputs71/100
5 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › vendor_credit_id
Id of an existing vendor credit. Find it with search_vendor_credits.
Clear enough to supply this argument.
params › applications › items › bill_id
Open bill this credit offsets. Find it with search_bills.
Clear enough to supply this argument.
params › applications › items › amount
How much of the credit to apply to this bill. Partial is normal.
Clear enough to supply this argument.
params › txn_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › private_note
Not provided
Missing description. Explain what this value means and how to supply it.
params › bank_account_id
Payment account for the application. QuickBooks requires one even though a credit application moves no money and the total is zero. Omit and the company's first active bank account is used, reported back so the choice is visible.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "apply_vendor_credit",
"title": "Apply Vendor Credit",
"description": "Apply an existing vendor credit against one or more open bills in QuickBooks Online. This is the SECOND HALF of every vendor credit: QuickBooks does not offset a bill with a vendor credit by itself, so a credit recorded and not applied leaves both documents open in AP aging and the vendor balance uncorrected. Call this immediately after create_vendor_credit, in the same approval. Reports the credit's remaining balance afterwards so you can confirm the offset actually landed.On Xero this allocates the supplier credit against a bill. ONE bill per call: Xero's array writes are not all-or-nothing, so a multi-bill allocation that failed partway would spend part of the credit and still report an error. Applying it to a customer invoice is refused by name. txn_date, private_note and bank_account_id have no Xero equivalent - an allocation is dated today and simply offsets the bill - and are refused rather than dropped.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor_credit_id",
"applications",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"txn_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"applications": {
"type": "array",
"items": {
"type": "object",
"required": [
"bill_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"maximum": 999999999.99,
"description": "How much of the credit to apply to this bill. Partial is normal.",
"exclusiveMinimum": 0
},
"bill_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Open bill this credit offsets. Find it with search_bills."
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "One entry per bill being offset."
},
"private_note": {
"type": "string",
"maxLength": 4000
},
"bank_account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Payment account for the application. QuickBooks requires one even though a credit application moves no money and the total is zero. Omit and the company's first active bank account is used, reported back so the choice is visible."
},
"vendor_credit_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of an existing vendor credit. Find it with search_vendor_credits."
}
}
}
}
},
"annotations": {
"title": "Apply Vendor Credit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Create a deposit in QuickBooks Online. Use this to record incoming funds: customer payments, bank deposits, wire transfers, interest income. Requires DepositToAccountRef (the bank account receiving the deposit) and at least one Line item. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed. Class and department have DIFFERENT homes and QuickBooks rejects the whole request for getting either wrong (code 2010, measured 2026-09-10): ClassRef goes INSIDE each line's DepositLineDetail object, next to AccountRef, and so does the customer or vendor a line is for - as Entity, not CustomerRef. DepartmentRef is a DOCUMENT-level field: put it on the deposit, never on a line, which accepts it in neither position. TO BANK A PAYMENT THAT IS ALREADY IN QUICKBOOKS (one sitting in Undeposited Funds), do NOT code a line to the Undeposited Funds account - that is refused with "Select a bank account for this deposit". Link the payment instead, with a line that has no DepositLineDetail and no DetailType at all: { Amount: <the payment's amount>, LinkedTxn: [{ TxnId: "<payment id>", TxnLineId: "0", TxnType: "Payment" }] }. Measured 2026-09-13: TxnLineId is required and is the string "0", not a line number; omitting it fails the whole request (2020) and any other value fails it with "Transaction cannot be applied to Deposit". Ordinary income lines and linked-payment lines can sit on the same deposit. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company.
The description explains the capability, when to use it, and what to expect.
Inputs39/100
3 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › not_a_bank_line
Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book.
Clear enough to supply this argument.
params › deposit › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › Line
At least one line item required
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › deposit › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_deposit",
"title": "Create Deposit",
"description": "Create a deposit in QuickBooks Online. Use this to record incoming funds: customer payments, bank deposits, wire transfers, interest income. Requires DepositToAccountRef (the bank account receiving the deposit) and at least one Line item. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed. Class and department have DIFFERENT homes and QuickBooks rejects the whole request for getting either wrong (code 2010, measured 2026-09-10): ClassRef goes INSIDE each line's DepositLineDetail object, next to AccountRef, and so does the customer or vendor a line is for - as Entity, not CustomerRef. DepartmentRef is a DOCUMENT-level field: put it on the deposit, never on a line, which accepts it in neither position. TO BANK A PAYMENT THAT IS ALREADY IN QUICKBOOKS (one sitting in Undeposited Funds), do NOT code a line to the Undeposited Funds account - that is refused with \"Select a bank account for this deposit\". Link the payment instead, with a line that has no DepositLineDetail and no DetailType at all: { Amount: <the payment's amount>, LinkedTxn: [{ TxnId: \"<payment id>\", TxnLineId: \"0\", TxnType: \"Payment\" }] }. Measured 2026-09-13: TxnLineId is required and is the string \"0\", not a line number; omitting it fails the whole request (2020) and any other value fails it with \"Transaction cannot be applied to Deposit\". Ordinary income lines and linked-payment lines can sit on the same deposit. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"deposit",
"realm_id"
],
"properties": {
"deposit": {
"type": "object",
"required": [
"DepositToAccountRef",
"Line"
],
"properties": {
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "At least one line item required"
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account receiving the deposit"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book."
}
}
}
}
},
"annotations": {
"title": "Create Deposit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Get a deposit by Id from QuickBooks Online. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. For several deposits, use one search_deposits call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_deposit calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_deposit",
"title": "Get Deposit",
"description": "Get a deposit by Id from QuickBooks Online. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. For several deposits, use one search_deposits call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_deposit calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Deposit",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description71/100
Search deposits in QuickBooks Online that match given criteria. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Deposit entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Deposit entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_deposits",
"title": "Search Deposits",
"description": "Search deposits in QuickBooks Online that match given criteria. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Deposit entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Deposit entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Deposits",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Delete a deposit in QuickBooks Online. Use this to reverse a deposit that was booked in error, for example a bank feed line posted as income when it was a customer invoice payment or a transfer between accounts. Requires the deposit Id and its current SyncToken (get both from get_deposit or search_deposits). QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
2 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › deposit › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › SyncToken
Not provided
Missing description. Explain what this value means and how to supply it.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_deposit",
"title": "Delete Deposit",
"description": "Delete a deposit in QuickBooks Online. Use this to reverse a deposit that was booked in error, for example a bank feed line posted as income when it was a customer invoice payment or a transfer between accounts. Requires the deposit Id and its current SyncToken (get both from get_deposit or search_deposits). QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"deposit",
"realm_id"
],
"properties": {
"deposit": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,20}$"
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Deposit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Update a deposit in QuickBooks Online by Id. Use this to correct a deposit in place rather than deleting and re-creating it, which changes the document number and breaks anything that referenced it. Requires Id and SyncToken (get both from get_deposit or search_deposits). LINES ARE MERGED BY Id, NOT REPLACED, and this is measured: to edit a line, read the deposit and send that line back CARRYING THE Id get_deposit returned. A line without an Id is ADDED as a new line, which is how a re-code becomes a duplicate and doubles the deposit; a line you leave out is KEPT, not removed. Both are refused unless you pass amount_change_reason, so a value change is always deliberate. A DEPOSIT LINE CANNOT BE REMOVED through this API, and a line-level field such as the Entity ("Received From") name cannot be cleared - omitting it and sending null both leave it in place. To restructure a deposit's lines you have to delete the deposit and create it again, which changes its document number, or edit it in the QuickBooks website. To empty a TOP-LEVEL field such as PrivateNote or DocNumber, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. A line that BANKS AN EXISTING PAYMENT carries no DepositLineDetail and no DetailType - { Amount, LinkedTxn: [{ TxnId: "<payment id>", TxnLineId: "0", TxnType: "Payment" }] } - and TxnLineId is required and is the string "0". A line coded to the Undeposited Funds account instead is refused with "Select a bank account for this deposit". Removing such a line frees the payment again - measured 2026-09-13, it can be voided afterwards - and needs amount_change_reason, because the deposit's total changes. ClassRef goes INSIDE each line's DepositLineDetail object, and the customer or vendor a line is for goes there too, as Entity. DepartmentRef is a DOCUMENT-level field: put it on the deposit, never on a line. Measured 2026-09-10: either one in the wrong place fails the whole request with code 2010. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs52/100
7 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › deposit › Id
QBO Deposit ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › deposit › SyncToken
Optimistic concurrency token from get_deposit. QuickBooks rejects a stale one, which is the intended protection against two writers clobbering each other.
Clear enough to supply this argument.
params › deposit › Line
Lines to MERGE, not a replacement set. Each entry needs the Id get_deposit returned to edit that line; an entry without an Id is ADDED as a new line and an existing line you omit is kept. Omit Line entirely to leave the lines untouched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › deposit › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › deposit › DocNumber
Not provided
Missing description. Explain what this value means and how to supply it.
params › amount_change_reason
ONLY when the patch is meant to change what this deposit is worth -- including by ADDING a line, which is what a line without an Id does. Lines are merged by Id, so an unintended change is usually a line sent without its Id; it is refused unless you say here why the value should change. The reason is recorded.
Clear enough to supply this argument.
params › clear_fields
TOP-LEVEL field names to empty, for example PrivateNote or DocNumber. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id, SyncToken or line-level fields: a deposit line-level field cannot be emptied through this API at all, measured -- omitting it and sending null both leave it as it was.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_deposit",
"title": "Update Deposit",
"description": "Update a deposit in QuickBooks Online by Id. Use this to correct a deposit in place rather than deleting and re-creating it, which changes the document number and breaks anything that referenced it. Requires Id and SyncToken (get both from get_deposit or search_deposits). LINES ARE MERGED BY Id, NOT REPLACED, and this is measured: to edit a line, read the deposit and send that line back CARRYING THE Id get_deposit returned. A line without an Id is ADDED as a new line, which is how a re-code becomes a duplicate and doubles the deposit; a line you leave out is KEPT, not removed. Both are refused unless you pass amount_change_reason, so a value change is always deliberate. A DEPOSIT LINE CANNOT BE REMOVED through this API, and a line-level field such as the Entity (\"Received From\") name cannot be cleared - omitting it and sending null both leave it in place. To restructure a deposit's lines you have to delete the deposit and create it again, which changes its document number, or edit it in the QuickBooks website. To empty a TOP-LEVEL field such as PrivateNote or DocNumber, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. A line that BANKS AN EXISTING PAYMENT carries no DepositLineDetail and no DetailType - { Amount, LinkedTxn: [{ TxnId: \"<payment id>\", TxnLineId: \"0\", TxnType: \"Payment\" }] } - and TxnLineId is required and is the string \"0\". A line coded to the Undeposited Funds account instead is refused with \"Select a bank account for this deposit\". Removing such a line frees the payment again - measured 2026-09-13, it can be voided afterwards - and needs amount_change_reason, because the deposit's total changes. ClassRef goes INSIDE each line's DepositLineDetail object, and the customer or vendor a line is for goes there too, as Entity. DepartmentRef is a DOCUMENT-level field: put it on the deposit, never on a line. Measured 2026-09-10: either one in the wrong place fails the whole request with code 2010. QuickBooks only: Xero has no Deposit -- a Xero bank line is already one movement, so there is nothing to group -- and this tool says so by name on a Xero company. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"deposit",
"realm_id"
],
"properties": {
"deposit": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Deposit ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"minItems": 1,
"description": "Lines to MERGE, not a replacement set. Each entry needs the Id get_deposit returned to edit that line; an entry without an Id is ADDED as a new line and an existing line you omit is kept. Omit Line entirely to leave the lines untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"DocNumber": {
"type": "string",
"maxLength": 21
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_deposit. QuickBooks rejects a stale one, which is the intended protection against two writers clobbering each other."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account receiving the deposit."
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "TOP-LEVEL field names to empty, for example PrivateNote or DocNumber. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id, SyncToken or line-level fields: a deposit line-level field cannot be emptied through this API at all, measured -- omitting it and sending null both leave it as it was."
},
"amount_change_reason": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "ONLY when the patch is meant to change what this deposit is worth -- including by ADDING a line, which is what a line without an Id does. Lines are merged by Id, so an unintended change is usually a line sent without its Id; it is refused unless you say here why the value should change. The reason is recorded."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Deposit",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a transfer in QuickBooks Online. Use this to record fund movements between company bank accounts (e.g. checking to savings, checking to credit card payment). Requires FromAccountRef, ToAccountRef, and Amount. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a BankTransfer. Direction is carried by which account is From and which is To on both ledgers, so nothing is inferred; the amount must be positive and the two accounts must differ.
The description explains the capability, when to use it, and what to expect.
Inputs19/100
2 of 9 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › not_a_bank_line
Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › transfer › FromAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › FromAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › ToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › ToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_transfer",
"title": "Create Transfer",
"description": "Create a transfer in QuickBooks Online. Use this to record fund movements between company bank accounts (e.g. checking to savings, checking to credit card payment). Requires FromAccountRef, ToAccountRef, and Amount. If the company has a bank feed and this entry matches a bank line the feed has not booked yet (same register, amount and direction, within 5 days), the entry still posts, and that line is then recorded as booked by it, so the feed never posts the same money twice; the result names the line, and reverse_bank_booking on it releases the line if the match was wrong (the entry stays). Pass not_a_bank_line with a reason when the entry is not that bank transaction: nothing is claimed.On Xero this writes a BankTransfer. Direction is carried by which account is From and which is To on both ledgers, so nothing is inferred; the amount must be positive and the two accounts must differ.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transfer",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"transfer": {
"type": "object",
"required": [
"FromAccountRef",
"ToAccountRef",
"Amount"
],
"properties": {
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"ToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Destination account",
"additionalProperties": false
},
"FromAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Source account",
"additionalProperties": false
}
},
"additionalProperties": false
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when this entry is NOT the bank-feed transaction it happens to match - a correcting entry, an accrual reversal, or an entry predating the bank connection. Give the reason; it is recorded, and the matching feed line is left unclaimed for the feed to book."
}
}
}
}
},
"annotations": {
"title": "Create Transfer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Update a transfer between two accounts in QuickBooks Online by Id. Use this to correct a transfer in place - the wrong account, the wrong amount, the wrong date - rather than deleting and re-creating it. Requires Id and SyncToken (get both from get_transfer or search_transfers). To empty a field such as PrivateNote, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero cannot update a bank transfer at all - delete it and create it again. On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs38/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › transfer › Id
QBO Transfer ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › transfer › SyncToken
Optimistic concurrency token from get_transfer.
Clear enough to supply this argument.
params › transfer › FromAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › FromAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › ToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › ToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › clear_fields
Top-level field names to empty, for example PrivateNote. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_transfer",
"title": "Update Transfer",
"description": "Update a transfer between two accounts in QuickBooks Online by Id. Use this to correct a transfer in place - the wrong account, the wrong amount, the wrong date - rather than deleting and re-creating it. Requires Id and SyncToken (get both from get_transfer or search_transfers). To empty a field such as PrivateNote, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero cannot update a bank transfer at all - delete it and create it again. On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transfer",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"transfer": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Transfer ID"
},
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token from get_transfer."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"ToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Destination account."
},
"FromAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Source account."
}
},
"additionalProperties": {}
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to empty, for example PrivateNote. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Transfer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Update a customer payment in QuickBooks Online by Id. Use this to correct a receipt in place - the wrong date, the wrong bank account, or a receipt applied to the wrong invoice - rather than voiding it and entering it again, which loses the original reference and any deposit it was grouped into. Requires Id and SyncToken: get_payment returns both for a payment you have the id of. To find one, use search_bank_transactions on the account it was received into, which returns sync_token for each row -- for a payment not yet banked that is the Undeposited Funds account. SENDING Line REPLACES EVERY INVOICE APPLICATION on the payment, so include every application you want to keep, not just the new one. SUB-CUSTOMERS (jobs) constrain who the payer may be, and this bites on a patch that changes nothing else: a payment applied to a sub-customer's invoice cannot be moved to a SIBLING sub-customer, even by a sparse CustomerRef change with no Line in it - measured 2026-09-14, QuickBooks answers "You can't link a payment from a sub customer to an invoice for a different sub customer". Naming the PARENT customer instead is accepted and keeps the existing application; a parent's payment settles any of its sub-customers' invoices. To empty a top-level field such as PrivateNote or PaymentRefNum, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero cannot update a payment at all - delete it and record it again. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs48/100
8 of 14 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › payment › Id
QBO Payment ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › payment › SyncToken
Optimistic concurrency token. get_payment returns it, as does search_bank_transactions for each row.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payment › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › TotalAmt
Total received. Should equal the sum of Line amounts when fully applied.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payment › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › PaymentRefNum
Cheque or reference number.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payment › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › Line
Full replacement set of invoice applications - QuickBooks discards the existing ones. Omit to leave the applications untouched.
Clear enough to supply this argument.
params › clear_fields
Top-level field names to empty, for example PrivateNote or PaymentRefNum. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken.
Clear enough to supply this argument.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_payment",
"title": "Update Payment",
"description": "Update a customer payment in QuickBooks Online by Id. Use this to correct a receipt in place - the wrong date, the wrong bank account, or a receipt applied to the wrong invoice - rather than voiding it and entering it again, which loses the original reference and any deposit it was grouped into. Requires Id and SyncToken: get_payment returns both for a payment you have the id of. To find one, use search_bank_transactions on the account it was received into, which returns sync_token for each row -- for a payment not yet banked that is the Undeposited Funds account. SENDING Line REPLACES EVERY INVOICE APPLICATION on the payment, so include every application you want to keep, not just the new one. SUB-CUSTOMERS (jobs) constrain who the payer may be, and this bites on a patch that changes nothing else: a payment applied to a sub-customer's invoice cannot be moved to a SIBLING sub-customer, even by a sparse CustomerRef change with no Line in it - measured 2026-09-14, QuickBooks answers \"You can't link a payment from a sub customer to an invoice for a different sub customer\". Naming the PARENT customer instead is accepted and keeps the existing application; a parent's payment settles any of its sub-customers' invoices. To empty a top-level field such as PrivateNote or PaymentRefNum, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero cannot update a payment at all - delete it and record it again. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"payment",
"realm_id"
],
"properties": {
"payment": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO Payment ID"
},
"Line": {
"type": "array",
"items": {},
"maxItems": 200,
"description": "Full replacement set of invoice applications - QuickBooks discards the existing ones. Omit to leave the applications untouched."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number",
"maximum": 999999999.99,
"description": "Total received. Should equal the sum of Line amounts when fully applied.",
"exclusiveMinimum": 0
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token. get_payment returns it, as does search_bank_transactions for each row."
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer who paid."
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"PaymentRefNum": {
"type": "string",
"maxLength": 21,
"description": "Cheque or reference number."
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money landed in. Omit to leave it routed to Undeposited Funds."
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to empty, for example PrivateNote or PaymentRefNum. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken."
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Update Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Update a logged time activity in QuickBooks Online by Id. Use this to correct hours, the date the work was done, the customer it is billed to, or the billable status. Requires Id and SyncToken (get both from search_time_activities). Time activities had no reader at all before this release. To empty a top-level field such as Description, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.
The description explains the capability, when to use it, and what to expect.
Inputs25/100
6 of 19 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › time_activity › Id
QBO TimeActivity ID
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › time_activity › SyncToken
Optimistic concurrency token.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › time_activity › NameOf
Whether the time is an employee's or a vendor's.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › time_activity › EmployeeRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › EmployeeRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › VendorRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › VendorRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › TxnDate
The date the work was done, not today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › time_activity › Hours
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › Minutes
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › ItemRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › ItemRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › BillableStatus
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › HourlyRate
Not provided
Missing description. Explain what this value means and how to supply it.
params › time_activity › Description
Not provided
Missing description. Explain what this value means and how to supply it.
params › clear_fields
Top-level field names to empty, for example Description. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_time_activity",
"title": "Update Time Activity",
"description": "Update a logged time activity in QuickBooks Online by Id. Use this to correct hours, the date the work was done, the customer it is billed to, or the billable status. Requires Id and SyncToken (get both from search_time_activities). Time activities had no reader at all before this release. To empty a top-level field such as Description, name it in clear_fields; omitting a field never empties it, because ordinary updates are sparse. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"time_activity",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"clear_fields": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 20,
"minItems": 1,
"description": "Top-level field names to empty, for example Description. This costs an extra read and rewrites the record in full, so it is only for genuinely emptying a value - to CHANGE one, just send the new value. Cannot clear Id or SyncToken."
},
"time_activity": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QBO TimeActivity ID"
},
"Hours": {
"type": "integer",
"maximum": 999,
"minimum": 0
},
"NameOf": {
"enum": [
"Employee",
"Vendor"
],
"type": "string",
"description": "Whether the time is an employee's or a vendor's."
},
"ItemRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Service item, required for billable time."
},
"Minutes": {
"type": "integer",
"maximum": 59,
"minimum": 0
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The date the work was done, not today."
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,10}$",
"description": "Optimistic concurrency token."
},
"VendorRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Required when NameOf is Vendor."
},
"HourlyRate": {
"type": "number",
"maximum": 999999.99,
"minimum": 0
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer the time is billed to, if any."
},
"Description": {
"type": "string",
"maxLength": 4000
},
"EmployeeRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Required when NameOf is Employee."
},
"BillableStatus": {
"enum": [
"Billable",
"NotBillable",
"HasBeenBilled"
],
"type": "string"
}
},
"additionalProperties": {}
}
}
}
}
},
"annotations": {
"title": "Update Time Activity",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Search logged time activities in QuickBooks Online - hours recorded against an employee or vendor, optionally billable to a customer. Use this to answer questions about time logged in a period, to find unbilled billable time before invoicing, and to get the Id and SyncToken that update_time_activity needs. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online TimeActivity entity. One of: Id, TxnDate, CustomerRef, ItemRef, BillableStatus, HourlyRate, MetaData.CreateTime, MetaData.LastUpdatedTime, PayrollItemRef, Taxable. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online TimeActivity entity. One of: Id, TxnDate, CustomerRef, ItemRef, BillableStatus, HourlyRate, MetaData.CreateTime, MetaData.LastUpdatedTime, PayrollItemRef, Taxable. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_time_activities",
"title": "Search Time Activities",
"description": "Search logged time activities in QuickBooks Online - hours recorded against an employee or vendor, optionally billable to a customer. Use this to answer questions about time logged in a period, to find unbilled billable time before invoicing, and to get the Id and SyncToken that update_time_activity needs. Not available for Xero companies: Xero records time against a Project, in a separate API behind a `projects` scope this connector's token does not carry, so there is nothing to read or write there.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online TimeActivity entity. One of: Id, TxnDate, CustomerRef, ItemRef, BillableStatus, HourlyRate, MetaData.CreateTime, MetaData.LastUpdatedTime, PayrollItemRef, Taxable. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online TimeActivity entity. One of: Id, TxnDate, CustomerRef, ItemRef, BillableStatus, HourlyRate, MetaData.CreateTime, MetaData.LastUpdatedTime, PayrollItemRef, Taxable. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Time Activities",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Get a transfer by Id from QuickBooks Online.On Xero this reads one BankTransfer. For several transfers, use one search_transfers call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_transfer calls in parallel, which QuickBooks rate-limits (code 3001). On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_transfer",
"title": "Get Transfer",
"description": "Get a transfer by Id from QuickBooks Online.On Xero this reads one BankTransfer. For several transfers, use one search_transfers call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_transfer calls in parallel, which QuickBooks rate-limits (code 3001). On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Transfer",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Search transfers in QuickBooks Online that match given criteria.On Xero this reads BankTransfers. Filter on Id, TxnDate or MetaData.CreateTime; a Xero bank transfer has no last-updated timestamp, so MetaData.LastUpdatedTime is refused there. There is no account filter (FromAccountRef / ToAccountRef are not accepted fields, on either ledger; on Xero the two ends are nested objects its query language cannot reach): to find the transfers on one account, filter by TxnDate and match the accounts in the results.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
5 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › anyOf › 0 › field
Field to filter on - a property of the QuickBooks Online Transfer entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 0 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › anyOf › 0 › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › key
Field to filter on - a property of the QuickBooks Online Transfer entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › anyOf › 1 › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_transfers",
"title": "Search Transfers",
"description": "Search transfers in QuickBooks Online that match given criteria.On Xero this reads BankTransfers. Filter on Id, TxnDate or MetaData.CreateTime; a Xero bank transfer has no last-updated timestamp, so MetaData.LastUpdatedTime is refused there. There is no account filter (FromAccountRef / ToAccountRef are not accepted fields, on either ledger; on Xero the two ends are nested objects its query language cannot reach): to find the transfers on one account, filter by TxnDate and match the accounts in the results.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"anyOf": [
{
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Transfer entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Transfer entity. One of: Id, TxnDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
}
}
}
]
},
"description": "Filters to apply. Use {field, value, operator?} or legacy {key, value} pairs. For operator IN, pass value as an ARRAY of strings, not a comma-separated string -- a comma may belong to a single name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Transfers",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Delete a transfer in QuickBooks Online. Use this to reverse a transfer booked in error, for example a bank feed line posted as a move between two bank accounts when it was actually an expense or a customer payment. Requires the transfer Id and its current SyncToken (get both from get_transfer or search_transfers).On Xero this is REFUSED by name: Xero states a bank transfer can only be created, and the delete is not available on the endpoint this connector holds. Delete it in Xero directly, or post a reversing transfer. A false success here would leave the movement in the books while reporting it gone. On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
2 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › transfer › Id
Not provided
Missing description. Explain what this value means and how to supply it.
params › transfer › SyncToken
Not provided
Missing description. Explain what this value means and how to supply it.
params › reconciled_change_reason
Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_transfer",
"title": "Delete Transfer",
"description": "Delete a transfer in QuickBooks Online. Use this to reverse a transfer booked in error, for example a bank feed line posted as a move between two bank accounts when it was actually an expense or a customer payment. Requires the transfer Id and its current SyncToken (get both from get_transfer or search_transfers).On Xero this is REFUSED by name: Xero states a bank transfer can only be created, and the delete is not available on the endpoint this connector holds. Delete it in Xero directly, or post a reversing transfer. A false success here would leave the movement in the books while reporting it gone. On QuickBooks the Id must be a Transfer's: QuickBooks numbers every transaction type from one sequence, and an id of another type is refused before anything is read or changed, naming the tool for its type. If the transaction belongs to a finished reconciliation, this is refused unless reconciled_change_reason says why - QuickBooks itself would accept it and leave the reconciliation out of balance with no warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transfer",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"transfer": {
"type": "object",
"required": [
"Id",
"SyncToken"
],
"properties": {
"Id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"SyncToken": {
"type": "string",
"pattern": "^\\d{1,20}$"
}
},
"additionalProperties": {}
},
"reconciled_change_reason": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Why this change is meant, when the transaction belongs to a FINISHED reconciliation (Clr = R). Without it, that one write is refused -- QuickBooks accepts it silently and the reconciliation then no longer balances. Send it only if you will fix the reconciliation yourself; the ordinary route is to undo the reconciliation in QuickBooks first. Leave it out otherwise: it is never needed for a transaction that is not reconciled."
}
}
}
}
},
"annotations": {
"title": "Delete Transfer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a customer payment in QuickBooks Online and apply it to open invoices. Use this when money received from a customer settles an invoice: bank feed receipts, cheques, card settlements, wire receipts. Do NOT use create_deposit for these — booking a customer receipt as a deposit to an income account double counts the revenue and leaves the invoice open, overstating accounts receivable. Requires CustomerRef and TotalAmt; supply Line entries with LinkedTxn to apply the money to specific invoices. With SUB-CUSTOMERS (jobs), the payer must be the invoice's own customer or its PARENT: a payment from one sub-customer applied to a sibling sub-customer's invoice is refused with code 620 "TxnID Cannot Be Linked", naming the invoice id and nothing else (measured 2026-09-14). A parent's payment settling a sub-customer's invoice is accepted.On Xero this writes a Payment against a specific invoice (ACCRECPAYMENT). ONE invoice per call: Xero's array write is not all-or-nothing, so a multi-invoice receipt that failed partway would settle some and still report an error. Xero has no unapplied customer payment - money on account is a prepayment or overpayment, a different document - so a payment naming no invoice is refused rather than parked. Settling a supplier bill through this tool is refused by name.
Resolve contradictions between the description, input schema, and annotations.
Inputs23/100
3 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › payment › CustomerRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › CustomerRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › TotalAmt
Total amount received. Should equal the sum of Line amounts when fully applied.
Clear enough to supply this argument.
params › payment › DepositToAccountRef › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › DepositToAccountRef › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › PaymentRefNum
Cheque or reference number
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payment › TxnDate
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › PrivateNote
Not provided
Missing description. Explain what this value means and how to supply it.
params › payment › Line › items › Amount
Not provided
Missing description. Explain what this value means and how to supply it.
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_payment",
"title": "Create Payment",
"description": "Create a customer payment in QuickBooks Online and apply it to open invoices. Use this when money received from a customer settles an invoice: bank feed receipts, cheques, card settlements, wire receipts. Do NOT use create_deposit for these — booking a customer receipt as a deposit to an income account double counts the revenue and leaves the invoice open, overstating accounts receivable. Requires CustomerRef and TotalAmt; supply Line entries with LinkedTxn to apply the money to specific invoices. With SUB-CUSTOMERS (jobs), the payer must be the invoice's own customer or its PARENT: a payment from one sub-customer applied to a sibling sub-customer's invoice is refused with code 620 \"TxnID Cannot Be Linked\", naming the invoice id and nothing else (measured 2026-09-14). A parent's payment settling a sub-customer's invoice is accepted.On Xero this writes a Payment against a specific invoice (ACCRECPAYMENT). ONE invoice per call: Xero's array write is not all-or-nothing, so a multi-invoice receipt that failed partway would settle some and still report an error. Xero has no unapplied customer payment - money on account is a prepayment or overpayment, a different document - so a payment naming no invoice is refused rather than parked. Settling a supplier bill through this tool is refused by name.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"payment",
"realm_id"
],
"properties": {
"payment": {
"type": "object",
"required": [
"CustomerRef",
"TotalAmt"
],
"properties": {
"Line": {
"type": "array",
"items": {
"type": "object",
"required": [
"Amount",
"LinkedTxn"
],
"properties": {
"Amount": {
"type": "number",
"maximum": 999999999.99,
"exclusiveMinimum": 0
},
"LinkedTxn": {
"type": "array",
"items": {
"type": "object",
"required": [
"TxnId",
"TxnType"
],
"properties": {
"TxnId": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
},
"TxnType": {
"type": "string",
"const": "Invoice"
}
},
"additionalProperties": {}
},
"maxItems": 10,
"minItems": 1,
"description": "Invoice(s) this line settles"
}
},
"additionalProperties": {}
},
"maxItems": 200,
"description": "Invoice applications. Omit to leave the payment unapplied as a customer credit, which leaves AR overstated — prefer applying it."
},
"TxnDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"TotalAmt": {
"type": "number",
"maximum": 999999999.99,
"description": "Total amount received. Should equal the sum of Line amounts when fully applied.",
"exclusiveMinimum": 0
},
"CustomerRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Customer who paid"
},
"PrivateNote": {
"type": "string",
"maxLength": 4000
},
"PaymentRefNum": {
"type": "string",
"maxLength": 21,
"description": "Cheque or reference number"
},
"DepositToAccountRef": {
"type": "object",
"required": [
"value"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200
},
"value": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
}
},
"description": "Bank account the money landed in. Omit to route the receipt to Undeposited Funds instead - one left there is banked later with create_deposit, as a line of { Amount, LinkedTxn: [{ TxnId: \"<this payment's id>\", TxnLineId: \"0\", TxnType: \"Payment\" }] } and no DepositLineDetail."
}
},
"additionalProperties": {}
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Create Payment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Upload a file to QuickBooks Online and attach it to a transaction. Requires a 'handle' issued by generate_attachment — the server streams the file to QBO without routing the payload through the tool call. Workflow: generate_attachment → upload_attachable(handle, entity_type, entity_id).THE HANDLE COMES FROM ONE OF TWO TOOLS, and no parameter here takes file content directly. generate_attachment renders a document from structured content you supply; request_attachment_upload gives you a one-time URL for a file the USER already has, which you PUT from your sandbox. Both return an att_ handle this tool accepts, on QuickBooks and Xero alike. A HANDLE EXPIRES 1 HOUR AFTER IT IS ISSUED: call this straight after the generate_attachment or upload PUTs, not an hour later. SEVERAL FILES ARE ONE CALL: pass attachments: [{ handle, entity_type, entity_id }, ...], one entry per file (each may also carry filename, also_attach_to and overwrite), instead of handle/entity_type/entity_id. Use it after request_attachment_upload with files, or after several generate_attachment calls. The result lists what was attached and, by handle, anything that was not, so only those need redoing. ON XERO A REPEAT FILENAME REPLACES the existing attachment silently -- the filename is the address on that API -- so a collision is refused here and you choose: a different filename, or overwrite: true. Nothing is uploaded by the refusal. ONE DOCUMENT ON SEVERAL TRANSACTIONS IS ONE CALL: list the others in also_attach_to. A handle can only be redeemed once, so re-sending it for the next transaction fails - and re-generating the document for each one leaves QuickBooks holding a separate copy per transaction, which is what a real caller did thirteen times on 2026-09-13. On QuickBooks the extras cost one more API call and no second copy of the file (measured 2026-09-14: one Attachable carries many transactions). On Xero each document stores its own copy because attachments live on the document there, so the same call uploads the bytes once per target. Works on Xero too, writing to the document's own Attachments path. The same entity types are accepted and mapped as for get_attachments. The upload is deliberately NOT retried on Xero: unlike a rejected write, a PUT that timed out may already have stored the file, and retrying would attach it twice under one name with no way to tell from outside.
The description explains the capability, when to use it, and what to expect.
Inputs81/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › handle
One file: the attachment handle issued by generate_attachment or request_attachment_upload. For several files use attachments instead.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › filename
Optional filename override. Defaults to the filename recorded when the handle was issued.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › content_type
Optional MIME type override. Defaults to the content type recorded when the handle was issued.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › entity_type
One file: the entity type to attach it to
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › entity_id
One file: the entity ID to attach it to
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › attachments › items › handle
This file's att_ handle
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › attachments › items › entity_type
Entity type to attach this file to
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › attachments › items › entity_id
Entity ID to attach this file to
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › attachments › items › filename
Optional filename override. Defaults to the filename recorded when the handle was issued.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › attachments › items › overwrite
Xero only: replace an attachment this document already has under the same filename
Clear enough to supply this argument.
params › also_attach_to › items › entity_type
Entity type of the further transaction
Clear enough to supply this argument.
params › also_attach_to › items › entity_id
Id of the further transaction
Clear enough to supply this argument.
params › overwrite
Xero only, and ignored on QuickBooks. A Xero document addresses its attachments BY FILENAME, so uploading a name it already carries replaces that file and the original cannot be recovered (measured 2026-09-03) - a collision is refused unless you pass true here. QuickBooks keeps both instead, each with its own id (measured the same day), so nothing is refused there and a repeat name simply leaves two.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "upload_attachable",
"title": "Upload Attachment",
"description": "Upload a file to QuickBooks Online and attach it to a transaction. Requires a 'handle' issued by generate_attachment — the server streams the file to QBO without routing the payload through the tool call. Workflow: generate_attachment → upload_attachable(handle, entity_type, entity_id).THE HANDLE COMES FROM ONE OF TWO TOOLS, and no parameter here takes file content directly. generate_attachment renders a document from structured content you supply; request_attachment_upload gives you a one-time URL for a file the USER already has, which you PUT from your sandbox. Both return an att_ handle this tool accepts, on QuickBooks and Xero alike. A HANDLE EXPIRES 1 HOUR AFTER IT IS ISSUED: call this straight after the generate_attachment or upload PUTs, not an hour later. SEVERAL FILES ARE ONE CALL: pass attachments: [{ handle, entity_type, entity_id }, ...], one entry per file (each may also carry filename, also_attach_to and overwrite), instead of handle/entity_type/entity_id. Use it after request_attachment_upload with files, or after several generate_attachment calls. The result lists what was attached and, by handle, anything that was not, so only those need redoing. ON XERO A REPEAT FILENAME REPLACES the existing attachment silently -- the filename is the address on that API -- so a collision is refused here and you choose: a different filename, or overwrite: true. Nothing is uploaded by the refusal. ONE DOCUMENT ON SEVERAL TRANSACTIONS IS ONE CALL: list the others in also_attach_to. A handle can only be redeemed once, so re-sending it for the next transaction fails - and re-generating the document for each one leaves QuickBooks holding a separate copy per transaction, which is what a real caller did thirteen times on 2026-09-13. On QuickBooks the extras cost one more API call and no second copy of the file (measured 2026-09-14: one Attachable carries many transactions). On Xero each document stores its own copy because attachments live on the document there, so the same call uploads the bytes once per target. Works on Xero too, writing to the document's own Attachments path. The same entity types are accepted and mapped as for get_attachments. The upload is deliberately NOT retried on Xero: unlike a rejected write, a PUT that timed out may already have stored the file, and retrying would attach it twice under one name with no way to tell from outside.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"handle": {
"type": "string",
"pattern": "^att_[a-f0-9]{32}$",
"description": "One file: the attachment handle issued by generate_attachment or request_attachment_upload. For several files use attachments instead."
},
"filename": {
"type": "string",
"pattern": "^[a-zA-Z0-9._\\s-]+$",
"maxLength": 200,
"description": "Optional filename override. Defaults to the filename recorded when the handle was issued."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "One file: the entity ID to attach it to"
},
"overwrite": {
"type": "boolean",
"description": "Xero only, and ignored on QuickBooks. A Xero document addresses its attachments BY FILENAME, so uploading a name it already carries replaces that file and the original cannot be recovered (measured 2026-09-03) - a collision is refused unless you pass true here. QuickBooks keeps both instead, each with its own id (measured the same day), so nothing is refused there and a repeat name simply leaves two."
},
"attachments": {
"type": "array",
"items": {
"type": "object",
"required": [
"handle",
"entity_type",
"entity_id"
],
"properties": {
"handle": {
"type": "string",
"pattern": "^att_[a-f0-9]{32}$",
"description": "This file's att_ handle"
},
"filename": {
"type": "string",
"pattern": "^[a-zA-Z0-9._\\s-]+$",
"maxLength": 200,
"description": "Optional filename override. Defaults to the filename recorded when the handle was issued."
},
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Entity ID to attach this file to"
},
"overwrite": {
"type": "boolean",
"description": "Xero only: replace an attachment this document already has under the same filename"
},
"entity_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"JournalEntry",
"Invoice",
"Bill",
"Estimate",
"VendorCredit",
"CreditMemo",
"SalesReceipt",
"RefundReceipt",
"Payment"
],
"type": "string",
"description": "Entity type to attach this file to"
},
"also_attach_to": {
"type": "array",
"items": {
"type": "object",
"required": [
"entity_type",
"entity_id"
],
"properties": {
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the further transaction"
},
"entity_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"JournalEntry",
"Invoice",
"Bill",
"Estimate",
"VendorCredit",
"CreditMemo",
"SalesReceipt",
"RefundReceipt",
"Payment"
],
"type": "string",
"description": "Entity type of the further transaction"
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "Further transactions THIS file should also appear on"
}
}
},
"maxItems": 25,
"minItems": 1,
"description": "Several files in one call: one { handle, entity_type, entity_id } per file. Use instead of handle/entity_type/entity_id when there is more than one file. One file failing does not stop the others; the result names each one that did not attach."
},
"entity_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"JournalEntry",
"Invoice",
"Bill",
"Estimate",
"VendorCredit",
"CreditMemo",
"SalesReceipt",
"RefundReceipt",
"Payment"
],
"type": "string",
"description": "One file: the entity type to attach it to"
},
"content_type": {
"type": "string",
"pattern": "^[a-z]+\\/[a-z0-9.+-]+$",
"description": "Optional MIME type override. Defaults to the content type recorded when the handle was issued."
},
"also_attach_to": {
"type": "array",
"items": {
"type": "object",
"required": [
"entity_type",
"entity_id"
],
"properties": {
"entity_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Id of the further transaction"
},
"entity_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"JournalEntry",
"Invoice",
"Bill",
"Estimate",
"VendorCredit",
"CreditMemo",
"SalesReceipt",
"RefundReceipt",
"Payment"
],
"type": "string",
"description": "Entity type of the further transaction"
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "Further transactions the SAME file should appear on, so one document does not become one copy per transaction. Each entry is { entity_type, entity_id }; duplicates of the primary target are ignored. On QuickBooks this adds links to the one uploaded file; on Xero, where an attachment belongs to the document, the bytes are uploaded once per target and each keeps its own filename-collision check."
}
}
}
}
},
"annotations": {
"title": "Upload Attachment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Generate a PDF or XLSX file from structured content and store it server-side for attaching to a QBO entity via upload_attachable. Use this INSTEAD of returning base64 when the output is larger than ~50 KB — it keeps the payload out of the tool-call response. Returns a handle (att_...) that upload_attachable accepts. Handle expires after 1 hour.Works for QuickBooks Online and Xero companies alike - it renders the file and never queries either ledger. The handle it returns is accepted by upload_attachable on both. IT RENDERS A FILE, IT DOES NOT CARRY ONE. This tool composes a document from the content you pass it. For a file that already exists - a PDF the user attached to the chat, a scan, a supplier's invoice - use request_attachment_upload instead: it returns a one-time URL you PUT the bytes to, and hands back the same kind of handle. Do not re-type somebody's document through this tool and attach it as though it were the original; a transcription that looks like the source document is worse than no attachment. PDFs it renders carry the firm's letterhead - name and uploaded logo - by default; pass brand:false for a plain page. Do not tell a user their firm has no logo on the strength of this tool's output: no tool here reports firm branding, so you cannot know.
The description explains the capability, when to use it, and what to expect.
Inputs71/100
15 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › format
Output format. pdf for documents, xlsx for spreadsheets
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › filename
File name (extension optional — will be added if missing). Example: 'march-expenses-by-class'
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › pdf › title
Document title, shown as the main heading
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › pdf › subtitle
Optional subtitle shown under the title
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › pdf › sections › items › heading
Optional section heading
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › pdf › sections › items › paragraphs
Body paragraphs for this section
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › pdf › sections › items › bullets
Bullet list items
Explain the meaning of this value, not just its name.
params › pdf › sections › items › table › headers
Not provided
Missing description. Explain what this value means and how to supply it.
params › pdf › sections › items › table › rows
Not provided
Missing description. Explain what this value means and how to supply it.
params › pdf › footer
Optional footer text shown on every page
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Optional column width in characters. Default: header length + 2
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › xlsx › sheets › items › rows
Data rows keyed by column key
Clear enough to supply this argument.
params › brand
Put the firm's name and uploaded logo on the PDF letterhead. DEFAULT TRUE — omit it and the document is branded. Pass false only for a page that must not look like it came from the firm. Ignored for xlsx (the firm name goes in the file's author metadata either way).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "generate_attachment",
"title": "Generate Attachment",
"description": "Generate a PDF or XLSX file from structured content and store it server-side for attaching to a QBO entity via upload_attachable. Use this INSTEAD of returning base64 when the output is larger than ~50 KB — it keeps the payload out of the tool-call response. Returns a handle (att_...) that upload_attachable accepts. Handle expires after 1 hour.Works for QuickBooks Online and Xero companies alike - it renders the file and never queries either ledger. The handle it returns is accepted by upload_attachable on both. IT RENDERS A FILE, IT DOES NOT CARRY ONE. This tool composes a document from the content you pass it. For a file that already exists - a PDF the user attached to the chat, a scan, a supplier's invoice - use request_attachment_upload instead: it returns a one-time URL you PUT the bytes to, and hands back the same kind of handle. Do not re-type somebody's document through this tool and attach it as though it were the original; a transcription that looks like the source document is worse than no attachment. PDFs it renders carry the firm's letterhead - name and uploaded logo - by default; pass brand:false for a plain page. Do not tell a user their firm has no logo on the strength of this tool's output: no tool here reports firm branding, so you cannot know.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"format",
"filename",
"realm_id"
],
"properties": {
"pdf": {
"type": "object",
"required": [
"title",
"sections"
],
"properties": {
"title": {
"type": "string",
"maxLength": 200,
"description": "Document title, shown as the main heading"
},
"footer": {
"type": "string",
"maxLength": 500,
"description": "Optional footer text shown on every page"
},
"sections": {
"type": "array",
"items": {
"type": "object",
"properties": {
"table": {
"type": "object",
"required": [
"headers",
"rows"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": [
"string",
"number"
]
}
},
"maxItems": 500
},
"headers": {
"type": "array",
"items": {
"type": "string",
"maxLength": 100
},
"maxItems": 20,
"minItems": 1
}
},
"description": "Optional table with header row and data rows"
},
"bullets": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2000
},
"maxItems": 100,
"description": "Bullet list items"
},
"heading": {
"type": "string",
"maxLength": 200,
"description": "Optional section heading"
},
"paragraphs": {
"type": "array",
"items": {
"type": "string",
"maxLength": 5000
},
"maxItems": 50,
"description": "Body paragraphs for this section"
}
}
},
"maxItems": 50,
"minItems": 1,
"description": "Ordered list of content sections (headings, paragraphs, bullets, tables)"
},
"subtitle": {
"type": "string",
"maxLength": 500,
"description": "Optional subtitle shown under the title"
}
},
"description": "PDF body (structured content). Required when format='pdf'"
},
"xlsx": {
"type": "object",
"required": [
"sheets"
],
"properties": {
"sheets": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"columns",
"rows"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"description": "Sheet tab name. Truncated to 31 chars by Excel"
},
"rows": {
"type": "array",
"items": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": [
"string",
"number",
"boolean",
"null"
]
}
},
"maxItems": 10000,
"description": "Data rows keyed by column key"
},
"columns": {
"type": "array",
"items": {
"type": "object",
"required": [
"header",
"key"
],
"properties": {
"key": {
"type": "string",
"pattern": "^[a-zA-Z_][a-zA-Z0-9_]*$",
"maxLength": 64,
"description": "Column key used to map row objects to this column"
},
"width": {
"type": "integer",
"maximum": 80,
"minimum": 4,
"description": "Optional column width in characters. Default: header length + 2"
},
"header": {
"type": "string",
"maxLength": 100,
"description": "Column header label shown in row 1"
}
}
},
"maxItems": 30,
"minItems": 1
}
}
},
"maxItems": 20,
"minItems": 1
}
},
"description": "XLSX body (sheets + columns + rows). Required when format='xlsx'"
},
"brand": {
"type": "boolean",
"description": "Put the firm's name and uploaded logo on the PDF letterhead. DEFAULT TRUE — omit it and the document is branded. Pass false only for a page that must not look like it came from the firm. Ignored for xlsx (the firm name goes in the file's author metadata either way)."
},
"format": {
"enum": [
"pdf",
"xlsx"
],
"type": "string",
"description": "Output format. pdf for documents, xlsx for spreadsheets"
},
"filename": {
"type": "string",
"pattern": "^[a-zA-Z0-9._\\s-]+$",
"maxLength": 200,
"description": "File name (extension optional — will be added if missing). Example: 'march-expenses-by-class'"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Generate Attachment",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Get the PDF the ledger renders for an invoice or an estimate (a quote on Xero) - the same document the customer receives, with the company's own template and logo. Works on QuickBooks Online and Xero. Returns two things, never the bytes: a download link for the user, valid 24 hours (give it to them when they want the PDF), and an attachment handle (att_...) for upload_attachable, valid 1 hour, like a handle from generate_attachment. Read-only; it changes nothing in the ledger. Use the record's Id from search_invoices / search_estimates (QuickBooks Id, or Xero InvoiceID / QuoteID), not the document number. For several, make the calls one at a time, not in parallel: QuickBooks rate-limits a parallel burst (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › type
Which document: invoice or estimate
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › id
The Id of the invoice or estimate (QuickBooks Id, or Xero InvoiceID / QuoteID; not its number)
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_document_pdf",
"title": "Get Document Pdf",
"description": "Get the PDF the ledger renders for an invoice or an estimate (a quote on Xero) - the same document the customer receives, with the company's own template and logo. Works on QuickBooks Online and Xero. Returns two things, never the bytes: a download link for the user, valid 24 hours (give it to them when they want the PDF), and an attachment handle (att_...) for upload_attachable, valid 1 hour, like a handle from generate_attachment. Read-only; it changes nothing in the ledger. Use the record's Id from search_invoices / search_estimates (QuickBooks Id, or Xero InvoiceID / QuoteID), not the document number. For several, make the calls one at a time, not in parallel: QuickBooks rate-limits a parallel burst (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"type",
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The Id of the invoice or estimate (QuickBooks Id, or Xero InvoiceID / QuoteID; not its number)"
},
"type": {
"enum": [
"invoice",
"estimate"
],
"type": "string",
"description": "Which document: invoice or estimate"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Document Pdf",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description64/100
Get a one-time URL for uploading a file the USER already has - a supplier's PDF, a scan, a receipt photo - so it can be attached to a QuickBooks Online or Xero record. Use this when the user has attached a document to the conversation and wants THAT document on the record. For a document you are writing yourself (a memo, a summary, a schedule), use generate_attachment instead - it needs no upload. HOW IT WORKS, in three steps: (1) call this tool with the filename and content type; (2) upload the file's bytes to the URL it returns, with a PUT, from your code-execution sandbox where the user's attachment is on disk - the response gives you an att_ handle; (3) call upload_attachable with that handle and the entity to attach it to, STRAIGHT AFTER the PUT. The handle expires 1 hour after the upload. SEVERAL FILES: pass them all in files: [{ filename, content_type }, ...] in ONE call, upload them all in ONE sandbox run with the commands it returns, then attach them all in ONE upload_attachable call (attachments: [...]). That is three steps for any number of files instead of three per file, and it finishes well inside the hour. THE URL IS THIS CONNECTOR'S OWN SERVER, the same host that serves these tools, and the upload is the connector's documented attachment path rather than an arbitrary third-party endpoint. It is single-use, expires in ten minutes, accepts one file, and is bound to the company and user this tool call was made for. If your environment cannot make outbound requests, say so plainly and tell the user to attach the file in QuickBooks or Xero directly - do not re-create their document from what you read and present it as the original.
Resolve contradictions between the description, input schema, and annotations.
Inputs84/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › filename
One file: its name. For several files use files instead
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › content_type
One file: its MIME type. For several files use files instead
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › files › items › filename
The file's name, used as the attachment name on the ledger
Clear enough to supply this argument.
params › files › items › content_type
The file's MIME type. The ledger is told this; the upload cannot override it
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "request_attachment_upload",
"title": "Request Attachment Upload",
"description": "Get a one-time URL for uploading a file the USER already has - a supplier's PDF, a scan, a receipt photo - so it can be attached to a QuickBooks Online or Xero record. Use this when the user has attached a document to the conversation and wants THAT document on the record. For a document you are writing yourself (a memo, a summary, a schedule), use generate_attachment instead - it needs no upload. HOW IT WORKS, in three steps: (1) call this tool with the filename and content type; (2) upload the file's bytes to the URL it returns, with a PUT, from your code-execution sandbox where the user's attachment is on disk - the response gives you an att_ handle; (3) call upload_attachable with that handle and the entity to attach it to, STRAIGHT AFTER the PUT. The handle expires 1 hour after the upload. SEVERAL FILES: pass them all in files: [{ filename, content_type }, ...] in ONE call, upload them all in ONE sandbox run with the commands it returns, then attach them all in ONE upload_attachable call (attachments: [...]). That is three steps for any number of files instead of three per file, and it finishes well inside the hour. THE URL IS THIS CONNECTOR'S OWN SERVER, the same host that serves these tools, and the upload is the connector's documented attachment path rather than an arbitrary third-party endpoint. It is single-use, expires in ten minutes, accepts one file, and is bound to the company and user this tool call was made for. If your environment cannot make outbound requests, say so plainly and tell the user to attach the file in QuickBooks or Xero directly - do not re-create their document from what you read and present it as the original.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"filename",
"content_type"
],
"properties": {
"filename": {
"type": "string",
"pattern": "^[a-zA-Z0-9._\\s-]+$",
"maxLength": 200,
"minLength": 1,
"description": "The file's name, used as the attachment name on the ledger"
},
"content_type": {
"enum": [
"application/pdf",
"image/png",
"image/jpeg",
"image/gif",
"image/tiff",
"text/csv",
"text/plain",
"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
"application/vnd.openxmlformats-officedocument.wordprocessingml.document",
"application/msword",
"application/vnd.ms-excel"
],
"type": "string",
"description": "The file's MIME type. The ledger is told this; the upload cannot override it"
}
}
},
"maxItems": 25,
"minItems": 1,
"description": "Several files at once: one { filename, content_type } per file. Returns one upload URL each and one block of commands that uploads them all in a single sandbox run. Use this instead of filename/content_type whenever there is more than one file."
},
"filename": {
"type": "string",
"pattern": "^[a-zA-Z0-9._\\s-]+$",
"maxLength": 200,
"minLength": 1,
"description": "One file: its name. For several files use files instead"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"content_type": {
"enum": [
"application/pdf",
"image/png",
"image/jpeg",
"image/gif",
"image/tiff",
"text/csv",
"text/plain",
"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
"application/vnd.openxmlformats-officedocument.wordprocessingml.document",
"application/msword",
"application/vnd.ms-excel"
],
"type": "string",
"description": "One file: its MIME type. For several files use files instead"
}
}
}
}
},
"annotations": {
"title": "Request Attachment Upload",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Build an Excel workbook of QuickBooks Online or Xero financial statements in one call, with one sheet per report. Use this whenever someone asks for financials as a spreadsheet or an Excel file - a balance sheet and P&L for a period, a trial balance, a cash flow statement. The server pulls the reports and writes the workbook itself, so you do NOT need to read the reports first or assemble any rows: figures arrive as real numbers that sum and chart, not text. Returns a download link to give the user directly, valid 24 hours. It suits a request for a file, several statements together, or a class-filtered view. On Xero the cash_flow, general_ledger and transaction_list sheets cannot be built, and asking for any of them writes nothing; leave them out.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › report_types
Which statements to include, one sheet each, in the order given. Aging sheets list one row per customer or vendor with a column per aging bucket.
Clear enough to supply this argument.
params › start_date
Period start, for the sheets that cover a period. NOT EVERY SHEET DOES, and they are not wrong to differ: the P&L and P&L by class use the range; the balance sheet is as-of end_date; the trial balance is as-at end_date on Xero (a range is a QuickBooks-only thing there); and the two aging sheets are as-at end_date too. Each sheet prints the period it actually covers on its own first row, so a workbook mixing them says so.
Clear enough to supply this argument.
params › end_date
Period end, and the as-of date for the balance sheet. Default: today.
Clear enough to supply this argument.
params › accounting_method
Accounting method. Default: company preference. Take it from the client file.
Clear enough to supply this argument.
params › summarize_column_by
Column grouping, applied to the statements that support it. Default: Total.
Clear enough to supply this argument.
params › class_id
Restrict every sheet that supports it to one class. Look it up with search_classes.
Clear enough to supply this argument.
params › filename
Workbook filename. Default: financials-<end_date>.xlsx. The .xlsx extension is enforced.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "export_financials_xlsx",
"title": "Export Financials Xlsx",
"description": "Build an Excel workbook of QuickBooks Online or Xero financial statements in one call, with one sheet per report. Use this whenever someone asks for financials as a spreadsheet or an Excel file - a balance sheet and P&L for a period, a trial balance, a cash flow statement. The server pulls the reports and writes the workbook itself, so you do NOT need to read the reports first or assemble any rows: figures arrive as real numbers that sum and chart, not text. Returns a download link to give the user directly, valid 24 hours. It suits a request for a file, several statements together, or a class-filtered view. On Xero the cash_flow, general_ledger and transaction_list sheets cannot be built, and asking for any of them writes nothing; leave them out.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"report_types",
"realm_id"
],
"properties": {
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Restrict every sheet that supports it to one class. Look it up with search_classes."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end, and the as-of date for the balance sheet. Default: today."
},
"filename": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Workbook filename. Default: financials-<end_date>.xlsx. The .xlsx extension is enforced."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start, for the sheets that cover a period. NOT EVERY SHEET DOES, and they are not wrong to differ: the P&L and P&L by class use the range; the balance sheet is as-of end_date; the trial balance is as-at end_date on Xero (a range is a QuickBooks-only thing there); and the two aging sheets are as-at end_date too. Each sheet prints the period it actually covers on its own first row, so a workbook mixing them says so."
},
"report_types": {
"type": "array",
"items": {
"enum": [
"balance_sheet",
"profit_and_loss",
"profit_and_loss_by_class",
"trial_balance",
"cash_flow",
"general_ledger",
"transaction_list",
"ar_aging",
"ap_aging"
],
"type": "string"
},
"maxItems": 9,
"minItems": 1,
"description": "Which statements to include, one sheet each, in the order given. Aging sheets list one row per customer or vendor with a column per aging bucket."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference. Take it from the client file."
},
"summarize_column_by": {
"enum": [
"Total",
"Month",
"Quarter",
"Year"
],
"type": "string",
"description": "Column grouping, applied to the statements that support it. Default: Total."
}
}
}
}
},
"annotations": {
"title": "Export Financials Xlsx",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Build a finished HTML report page for an Artifact from QuickBooks Online or Xero: a Profit and Loss and/or a Balance Sheet, one to three sections, figures as of now. Use it when the user asks to see a report as an Artifact, page, dashboard or chart. The server runs the reports and fills the page: the figures, the ledger's own totals, and the Balance Sheet check (Total Assets = Total Liabilities and Equity, computed to the cent). The page checks a fingerprint of its figures when opened and shows a red banner if any figure was changed. Returns two text blocks: a summary (per section: status generated, partial, empty or blocked; the period; key figures; check results; what is missing) and the HTML. Publish the HTML unchanged; never type a figure into it. You may edit only title, observations and notes in its data, which the page labels as yours. period is required for every section: ask the user when they named none. Give start and end dates, an as_of date, or a macro (this_month, last_month, this_quarter, last_quarter, year_to_date, last_year, today), resolved on the server against the company's fiscal year; the page prints the dates. A report with no data for the period builds no page unless include_empty is true: create no Artifact and offer another period. A partial section says what may be missing. A blocked section shows the ledger's error.
The description explains the capability, when to use it, and what to expect.
Inputs77/100
10 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sections › items › report
Not provided
Missing description. Explain what this value means and how to supply it.
params › sections › items › period › start
First day, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sections › items › period › end
Last day, YYYY-MM-DD. A Balance Sheet is as of this date.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sections › items › period › as_of
One date, YYYY-MM-DD: a Balance Sheet as of it; a Profit and Loss from the start of that fiscal year to it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › sections › items › period › macro
A period shortcut, resolved on the server with the company's fiscal year.
Clear enough to supply this argument.
params › sections › items › accounting_method
QuickBooks only; Xero reports the basis set on the organisation and refuses this.
Explain the meaning of this value, not just its name.
params › sections › items › summarize_column_by
Columns, as on the report tools. Default Total.
Clear enough to supply this argument.
params › sections › items › class_id
QuickBooks only: one class. Look it up with search_classes.
Clear enough to supply this argument.
params › include_empty
Build the page even when a report has no data, showing an explicit empty state. Default false.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "build_report_page",
"title": "Build Report Page",
"description": "Build a finished HTML report page for an Artifact from QuickBooks Online or Xero: a Profit and Loss and/or a Balance Sheet, one to three sections, figures as of now. Use it when the user asks to see a report as an Artifact, page, dashboard or chart. The server runs the reports and fills the page: the figures, the ledger's own totals, and the Balance Sheet check (Total Assets = Total Liabilities and Equity, computed to the cent). The page checks a fingerprint of its figures when opened and shows a red banner if any figure was changed. Returns two text blocks: a summary (per section: status generated, partial, empty or blocked; the period; key figures; check results; what is missing) and the HTML. Publish the HTML unchanged; never type a figure into it. You may edit only title, observations and notes in its data, which the page labels as yours. period is required for every section: ask the user when they named none. Give start and end dates, an as_of date, or a macro (this_month, last_month, this_quarter, last_quarter, year_to_date, last_year, today), resolved on the server against the company's fiscal year; the page prints the dates. A report with no data for the period builds no page unless include_empty is true: create no Artifact and offer another period. A partial section says what may be missing. A blocked section shows the ledger's error.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"sections",
"realm_id"
],
"properties": {
"title": {
"type": "string",
"maxLength": 200,
"description": "Page title. Default: \"<first report> — <company> — <period>\"."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"sections": {
"type": "array",
"items": {
"type": "object",
"required": [
"report",
"period"
],
"properties": {
"period": {
"type": "object",
"properties": {
"end": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day, YYYY-MM-DD. A Balance Sheet is as of this date."
},
"as_of": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "One date, YYYY-MM-DD: a Balance Sheet as of it; a Profit and Loss from the start of that fiscal year to it."
},
"macro": {
"enum": [
"this_month",
"last_month",
"this_quarter",
"last_quarter",
"year_to_date",
"last_year",
"today"
],
"type": "string",
"description": "A period shortcut, resolved on the server with the company's fiscal year."
},
"start": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day, YYYY-MM-DD."
}
},
"description": "Required. start and end, as_of, or macro."
},
"report": {
"enum": [
"ProfitAndLoss",
"BalanceSheet"
],
"type": "string"
},
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "QuickBooks only: one class. Look it up with search_classes."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "QuickBooks only; Xero reports the basis set on the organisation and refuses this."
},
"summarize_column_by": {
"enum": [
"Total",
"Month",
"Quarter",
"Year",
"Classes"
],
"type": "string",
"description": "Columns, as on the report tools. Default Total."
}
}
},
"maxItems": 3,
"minItems": 1,
"description": "One to three reports, in page order."
},
"include_empty": {
"type": "boolean",
"description": "Build the page even when a report has no data, showing an explicit empty state. Default false."
}
}
}
}
},
"annotations": {
"title": "Build Report Page",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Pull Balance Sheet data from QuickBooks Online or Xero. Despite the qbo_ prefix in this tool's name it serves Xero organisations too. Returns structured JSON with assets, liabilities, and equity as of a date. On QuickBooks it supports class tracking: summarize_column_by Classes gives a column per class, and class_id filters to one. Xero's Balance Sheet takes the as-of date only: it reports the single accounting basis set on the organisation and slices by tracking category rather than by class, so accounting_method, class_id and any summarize_column_by other than Total are refused there with a reason rather than ignored. Internal working data for Claude's analysis - not displayed to users.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
As-of date in YYYY-MM-DD format. Default: today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › accounting_method
Accounting method. Default: company preference. QuickBooks only - Xero reports the single basis set on the organisation and refuses this.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › summarize_column_by
Column grouping for comparison views. Classes gives one column per class, for companies that track classes. Default: Total. QuickBooks only - on Xero anything other than Total is refused.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class_id
Filter to a single class by ID. Look it up with search_classes. Omit for all classes. QuickBooks only - Xero slices by tracking category and refuses this.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_balance_sheet",
"title": "Balance Sheet",
"description": "Pull Balance Sheet data from QuickBooks Online or Xero. Despite the qbo_ prefix in this tool's name it serves Xero organisations too. Returns structured JSON with assets, liabilities, and equity as of a date. On QuickBooks it supports class tracking: summarize_column_by Classes gives a column per class, and class_id filters to one. Xero's Balance Sheet takes the as-of date only: it reports the single accounting basis set on the organisation and slices by tracking category rather than by class, so accounting_method, class_id and any summarize_column_by other than Total are refused there with a reason rather than ignored. Internal working data for Claude's analysis - not displayed to users.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Filter to a single class by ID. Look it up with search_classes. Omit for all classes. QuickBooks only - Xero slices by tracking category and refuses this."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "As-of date in YYYY-MM-DD format. Default: today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference. QuickBooks only - Xero reports the single basis set on the organisation and refuses this."
},
"summarize_column_by": {
"enum": [
"Total",
"Month",
"Quarter",
"Year",
"Classes"
],
"type": "string",
"description": "Column grouping for comparison views. Classes gives one column per class, for companies that track classes. Default: Total. QuickBooks only - on Xero anything other than Total is refused."
}
}
}
}
},
"annotations": {
"title": "Balance Sheet",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Pull Profit and Loss (Income Statement) data from QuickBooks Online or Xero. Returns revenue, expenses, and net income for a period. Despite the qbo_ prefix in this tool's name it serves Xero organisations too. Use class_id to restrict it to one class; for a column per class use qbo_report_profit_and_loss_by_class instead. Xero reports the single accounting basis set on the organisation and slices by tracking category rather than by class, so accounting_method and class_id are refused there with a reason rather than ignored: leave both out for a Xero company. Internal working data for Claude's analysis - not displayed to users.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Period start in YYYY-MM-DD format. Default: start of the current fiscal year on both providers. On Xero that start is computed from the organisation's financial year end, because Xero's own default is the current month.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Period end in YYYY-MM-DD format. Default: today on QuickBooks; on Xero, the end of the current month.
Clear enough to supply this argument.
params › accounting_method
Accounting method. Default: company preference. QuickBooks only; Xero reports the basis set on the organisation and refuses this.
Explain the meaning of this value, not just its name.
params › summarize_column_by
Column grouping for comparison views. Default: Total. For a column per class use qbo_report_profit_and_loss_by_class instead. On Xero, Month/Quarter/Year columns are labelled with their date ranges, oldest first, plus a Total; start_date must be the 1st of a month, and at most 12 whole months/quarters/years fit in one report.
Clear enough to supply this argument.
params › class_id
Filter to a single class by ID. Look it up with search_classes. Omit for all classes. QuickBooks only; Xero has tracking categories instead of classes and refuses this.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_profit_and_loss",
"title": "Profit and Loss",
"description": "Pull Profit and Loss (Income Statement) data from QuickBooks Online or Xero. Returns revenue, expenses, and net income for a period. Despite the qbo_ prefix in this tool's name it serves Xero organisations too. Use class_id to restrict it to one class; for a column per class use qbo_report_profit_and_loss_by_class instead. Xero reports the single accounting basis set on the organisation and slices by tracking category rather than by class, so accounting_method and class_id are refused there with a reason rather than ignored: leave both out for a Xero company. Internal working data for Claude's analysis - not displayed to users.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Filter to a single class by ID. Look it up with search_classes. Omit for all classes. QuickBooks only; Xero has tracking categories instead of classes and refuses this."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end in YYYY-MM-DD format. Default: today on QuickBooks; on Xero, the end of the current month."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start in YYYY-MM-DD format. Default: start of the current fiscal year on both providers. On Xero that start is computed from the organisation's financial year end, because Xero's own default is the current month."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference. QuickBooks only; Xero reports the basis set on the organisation and refuses this."
},
"summarize_column_by": {
"enum": [
"Total",
"Month",
"Quarter",
"Year"
],
"type": "string",
"description": "Column grouping for comparison views. Default: Total. For a column per class use qbo_report_profit_and_loss_by_class instead. On Xero, Month/Quarter/Year columns are labelled with their date ranges, oldest first, plus a Total; start_date must be the 1st of a month, and at most 12 whole months/quarters/years fit in one report."
}
}
}
}
},
"annotations": {
"title": "Profit and Loss",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Pull Accounts Receivable aging from QuickBooks Online or Xero. Returns amounts owed by customer across aging buckets (Current, 1-30, 31-60, 61-90, 91+ days). Internal working data for Claude's analysis - not displayed to users. On Xero this is COMPUTED from the invoices themselves, because Xero has no whole-book aged receivables endpoint; it therefore cannot see amounts posted straight to the receivables control account. The result carries a reconciliation block comparing it with that account on Xero's own balance sheet - if it reports a difference, say so rather than presenting the report as tying to the balance sheet.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Report as-of date in YYYY-MM-DD format. Default: today. A past date gives the position as it stood on that day: on Xero, settlements made after it are added back, so the report describes that date rather than today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › aging_period
Days per aging bucket. Default: 30.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_ar_aging",
"title": "A/R Aging",
"description": "Pull Accounts Receivable aging from QuickBooks Online or Xero. Returns amounts owed by customer across aging buckets (Current, 1-30, 31-60, 61-90, 91+ days). Internal working data for Claude's analysis - not displayed to users. On Xero this is COMPUTED from the invoices themselves, because Xero has no whole-book aged receivables endpoint; it therefore cannot see amounts posted straight to the receivables control account. The result carries a reconciliation block comparing it with that account on Xero's own balance sheet - if it reports a difference, say so rather than presenting the report as tying to the balance sheet.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Report as-of date in YYYY-MM-DD format. Default: today. A past date gives the position as it stood on that day: on Xero, settlements made after it are added back, so the report describes that date rather than today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"aging_period": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Days per aging bucket. Default: 30.",
"exclusiveMinimum": 0
}
}
}
}
},
"annotations": {
"title": "A/R Aging",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Pull Accounts Payable aging from QuickBooks Online or Xero. Returns amounts owed to vendors across aging buckets (Current, 1-30, 31-60, 61-90, 91+ days). Internal working data for Claude's analysis - not displayed to users. On Xero this is COMPUTED from the bills themselves, because Xero has no whole-book aged payables endpoint; it therefore cannot see amounts posted straight to the payables control account (payroll liabilities and manual journals are the usual causes). The result carries a reconciliation block comparing it with that account on Xero's own balance sheet - if it reports a difference, say so rather than presenting the report as tying to the balance sheet.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Report as-of date in YYYY-MM-DD format. Default: today. A past date gives the position as it stood on that day: on Xero, settlements made after it are added back, so the report describes that date rather than today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › aging_period
Days per aging bucket. Default: 30.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_ap_aging",
"title": "A/P Aging",
"description": "Pull Accounts Payable aging from QuickBooks Online or Xero. Returns amounts owed to vendors across aging buckets (Current, 1-30, 31-60, 61-90, 91+ days). Internal working data for Claude's analysis - not displayed to users. On Xero this is COMPUTED from the bills themselves, because Xero has no whole-book aged payables endpoint; it therefore cannot see amounts posted straight to the payables control account (payroll liabilities and manual journals are the usual causes). The result carries a reconciliation block comparing it with that account on Xero's own balance sheet - if it reports a difference, say so rather than presenting the report as tying to the balance sheet.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Report as-of date in YYYY-MM-DD format. Default: today. A past date gives the position as it stood on that day: on Xero, settlements made after it are added back, so the report describes that date rather than today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"aging_period": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Days per aging bucket. Default: 30.",
"exclusiveMinimum": 0
}
}
}
}
},
"annotations": {
"title": "A/P Aging",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Pull the native Trial Balance report from QuickBooks Online (/reports/TrialBalance) or Xero (Reports/TrialBalance). Despite the qbo_ prefix in this tool's name it serves Xero organisations too. This is a real ledger report - always call this tool instead of constructing a trial balance manually. Returns every account with debit and credit columns for the specified period. Xero reports AS AT a single date, so pass end_date alone: start_date and accounting_method are refused there rather than ignored, and the Xero response carries both the period and the year-to-date debit and credit columns.
The description explains the capability, when to use it, and what to expect.
Inputs81/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Period start in YYYY-MM-DD format. Default: start of current fiscal year. QuickBooks only - Xero's Trial Balance is as at a single date and refuses this; pass end_date alone.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Period end in YYYY-MM-DD format. Default: today. On Xero this is the single as-at date the report is run for.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › accounting_method
Accounting method. Default: company preference. QuickBooks only - Xero reports the single basis set on the organisation and refuses this.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_trial_balance",
"title": "Trial Balance",
"description": "Pull the native Trial Balance report from QuickBooks Online (/reports/TrialBalance) or Xero (Reports/TrialBalance). Despite the qbo_ prefix in this tool's name it serves Xero organisations too. This is a real ledger report - always call this tool instead of constructing a trial balance manually. Returns every account with debit and credit columns for the specified period. Xero reports AS AT a single date, so pass end_date alone: start_date and accounting_method are refused there rather than ignored, and the Xero response carries both the period and the year-to-date debit and credit columns.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end in YYYY-MM-DD format. Default: today. On Xero this is the single as-at date the report is run for."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start in YYYY-MM-DD format. Default: start of current fiscal year. QuickBooks only - Xero's Trial Balance is as at a single date and refuses this; pass end_date alone."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference. QuickBooks only - Xero reports the single basis set on the organisation and refuses this."
}
}
}
}
},
"annotations": {
"title": "Trial Balance",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Search the budgets in a QuickBooks Online company or a Xero organisation. Returns each budget's id, name, period range and entry type — pass the id to get_budget for its lines, or to qbo_report_budget_vs_actuals to compare it against actuals. A company often holds several budgets, one per financial year, so check here before assuming which one a question is about. BudgetType is deliberately not offered as a filter: QuickBooks refuses it and leaks an internal service name when asked (measured). A Name filter is matched here rather than by QuickBooks, which silently returns nothing for a budget whose name contains the word "budget" — so "Operating budget" would otherwise look like it did not exist. Matching here also makes it case-insensitive. On Xero the list does not carry line counts — Xero returns budget lines only from the single-budget read — and the filters below are applied after the fetch, because Xero's Budgets endpoint takes no query.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
4 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › criteria › items › field
Field to filter on - a property of the QuickBooks Online Budget entity. One of: Id, Name, Active, StartDate, EndDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › criteria › items › value
Not provided
Missing description. Explain what this value means and how to supply it.
params › criteria › items › operator
Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › asc
Not provided
Missing description. Explain what this value means and how to supply it.
params › desc
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › offset
Not provided
Missing description. Explain what this value means and how to supply it.
params › count
Not provided
Missing description. Explain what this value means and how to supply it.
params › fetchAll
Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_budgets",
"title": "Search Budgets",
"description": "Search the budgets in a QuickBooks Online company or a Xero organisation. Returns each budget's id, name, period range and entry type — pass the id to get_budget for its lines, or to qbo_report_budget_vs_actuals to compare it against actuals. A company often holds several budgets, one per financial year, so check here before assuming which one a question is about. BudgetType is deliberately not offered as a filter: QuickBooks refuses it and leaks an internal service name when asked (measured). A Name filter is matched here rather than by QuickBooks, which silently returns nothing for a budget whose name contains the word \"budget\" — so \"Operating budget\" would otherwise look like it did not exist. Matching here also makes it case-insensitive. On Xero the list does not carry line counts — Xero returns budget lines only from the single-budget read — and the filters below are applied after the fetch, because Xero's Budgets endpoint takes no query.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"asc": {
"type": "string"
},
"desc": {
"type": "string"
},
"count": {
"type": "boolean"
},
"limit": {
"type": "number"
},
"offset": {
"type": "number"
},
"criteria": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"value"
],
"properties": {
"field": {
"type": "string",
"description": "Field to filter on - a property of the QuickBooks Online Budget entity. One of: Id, Name, Active, StartDate, EndDate, MetaData.CreateTime, MetaData.LastUpdatedTime. An unrecognised field is refused, not ignored."
},
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"type": "array",
"items": {
"type": [
"string",
"number"
]
},
"maxItems": 100,
"minItems": 1
}
]
},
"operator": {
"type": "string",
"description": "Comparison operator. One of: =, IN, <, >, <=, >=, LIKE. Common spellings are accepted and translated: equals, eq, is, gt, gte, lt, lte, contains, starts with, ends with. For IN, pass value as an ARRAY."
}
}
},
"description": "Filters to apply, as {field, value, operator?} triples. Omit criteria entirely to list every budget in the company — that is the usual call, since a company rarely has many. For operator IN, pass value as an ARRAY of strings, not a comma-separated string: a comma may belong to a single budget name, so a string is refused. Omit criteria entirely to return everything; an empty list [] means the same."
},
"fetchAll": {
"type": "boolean",
"description": "Return EVERY matching record rather than one page; the server pages through to the end, so the set is complete. Use it when the answer needs the whole set (a count, every vendor). Each record comes back in full, so on a large company a broad search can return thousands of documents, more than you can read in one response: narrow it first with a filter (a date range is usually enough), or leave this off and work through the results with limit and offset. On Xero it cannot be combined with offset."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Search Budgets",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Read one budget with its lines, from QuickBooks Online or Xero. Each line is an amount for one account in one period, and carries the class, customer or department it is budgeted against where the budget uses one. Returns the budget's sync_token, which update_budget requires. ON XERO, READ THE WINDOW: Xero returns only the periods inside the window asked for, and an unwindowed read returns a single month — so a Xero budget can look complete when it is not. This tool always sends an explicit window and reports it back as window_read; widen start_date/end_date to see more. For several budgets, use one search_budgets call with criteria [{field: "Id", operator: "IN", value: [the ids]}] rather than many get_budget calls in parallel, which QuickBooks rate-limits (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › budget_id
The budget's id, from search_budgets.
Clear enough to supply this argument.
params › start_date
Only lines on or after this date (YYYY-MM-DD). On Xero this is sent to Xero and limits what it returns; on QuickBooks the budget comes back whole and the filter is applied here.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Only lines on or before this date (YYYY-MM-DD).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_budget",
"title": "Get Budget",
"description": "Read one budget with its lines, from QuickBooks Online or Xero. Each line is an amount for one account in one period, and carries the class, customer or department it is budgeted against where the budget uses one. Returns the budget's sync_token, which update_budget requires. ON XERO, READ THE WINDOW: Xero returns only the periods inside the window asked for, and an unwindowed read returns a single month — so a Xero budget can look complete when it is not. This tool always sends an explicit window and reports it back as window_read; widen start_date/end_date to see more. For several budgets, use one search_budgets call with criteria [{field: \"Id\", operator: \"IN\", value: [the ids]}] rather than many get_budget calls in parallel, which QuickBooks rate-limits (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"budget_id",
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only lines on or before this date (YYYY-MM-DD)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"budget_id": {
"type": "string",
"description": "The budget's id, from search_budgets."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only lines on or after this date (YYYY-MM-DD). On Xero this is sent to Xero and limits what it returns; on QuickBooks the budget comes back whole and the filter is applied here."
}
}
}
}
},
"annotations": {
"title": "Get Budget",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Create a budget in QuickBooks Online, with its lines. Give the lines ONE of three ways: `lines` for explicit dated amounts, `accounts` for one array of amounts per account in period order (the shape a spreadsheet or CSV already has), or `spread` for a single annual figure per account that is divided across the periods. TWO THINGS TO KNOW BEFORE CALLING. (1) A budget line can be changed or zeroed later but NEVER removed — QuickBooks has no way to delete one, and an omitted line is left untouched rather than deleted, so only deleting the whole budget removes lines. Getting the accounts right matters more than getting the amounts right. (2) A budget may use only ONE of class, customer or department across all its lines; mixing them is refused by QuickBooks. Pass dry_run: true to see exactly what would be written — per account, per period, with totals — without writing anything. That is worth doing for an import from a file. Budgets created here are profit-and-loss budgets: QuickBooks' API accepts a balance-sheet budget type and silently stores a P&L budget instead, so that is refused rather than delivered wrong. Xero cannot create budgets through its API at all (the endpoint is GET-only); build those in Xero and read them here.
The description explains the capability, when to use it, and what to expect.
Inputs84/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › name
Budget name, e.g. "FY2027 Operating Budget".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
First day the budget covers (YYYY-MM-DD). It does NOT have to align to the fiscal year.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Last day the budget covers (YYYY-MM-DD).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › entry_type
Period grain: Monthly (default), Quarterly or Yearly. These are the only three QuickBooks accepts.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › budget_type
Leave unset. Only profit-and-loss budgets can be created through the API; anything else is refused rather than silently downgraded.
Resolve the mismatch between this description and its schema constraints.
params › lines › items › date
First day of the period this amount belongs to.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › lines › items › account_id
Account being budgeted. From search_accounts.
Clear enough to supply this argument.
params › lines › items › amount
Budgeted amount for this account in this period.
Clear enough to supply this argument.
params › lines › items › class_id
Class to budget against. Look it up with search_classes.
Clear enough to supply this argument.
params › lines › items › customer_id
Customer to budget against. Look it up with search_customers.
Clear enough to supply this argument.
params › lines › items › department_id
Department/location to budget against.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › accounts › items › account_id
Account being budgeted.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › accounts › items › amounts
One amount per period, in order, matching the number of periods between start_date and end_date.
Clear enough to supply this argument.
params › accounts › items › class_id
Class to budget against. Look it up with search_classes.
Clear enough to supply this argument.
params › accounts › items › customer_id
Customer to budget against. Look it up with search_customers.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › accounts › items › department_id
Department/location to budget against.
Clear enough to supply this argument.
params › spread › items › account_id
Account being budgeted.
Clear enough to supply this argument.
params › spread › items › annual_amount
Total for the whole budget window, divided evenly across its periods.
Clear enough to supply this argument.
params › spread › items › class_id
Class to budget against. Look it up with search_classes.
Clear enough to supply this argument.
params › spread › items › customer_id
Customer to budget against. Look it up with search_customers.
Clear enough to supply this argument.
params › spread › items › department_id
Department/location to budget against.
Clear enough to supply this argument.
params › dry_run
Return what would be written, and write nothing. Re-run the identical call without it to apply.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_budget",
"title": "Create Budget",
"description": "Create a budget in QuickBooks Online, with its lines. Give the lines ONE of three ways: `lines` for explicit dated amounts, `accounts` for one array of amounts per account in period order (the shape a spreadsheet or CSV already has), or `spread` for a single annual figure per account that is divided across the periods. TWO THINGS TO KNOW BEFORE CALLING. (1) A budget line can be changed or zeroed later but NEVER removed — QuickBooks has no way to delete one, and an omitted line is left untouched rather than deleted, so only deleting the whole budget removes lines. Getting the accounts right matters more than getting the amounts right. (2) A budget may use only ONE of class, customer or department across all its lines; mixing them is refused by QuickBooks. Pass dry_run: true to see exactly what would be written — per account, per period, with totals — without writing anything. That is worth doing for an import from a file. Budgets created here are profit-and-loss budgets: QuickBooks' API accepts a balance-sheet budget type and silently stores a P&L budget instead, so that is refused rather than delivered wrong. Xero cannot create budgets through its API at all (the endpoint is GET-only); build those in Xero and read them here.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"start_date",
"end_date",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Budget name, e.g. \"FY2027 Operating Budget\"."
},
"lines": {
"type": "array",
"items": {
"type": "object",
"required": [
"date",
"account_id",
"amount"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day of the period this amount belongs to."
},
"amount": {
"type": "number",
"description": "Budgeted amount for this account in this period."
},
"class_id": {
"type": "string",
"description": "Class to budget against. Look it up with search_classes."
},
"account_id": {
"type": "string",
"description": "Account being budgeted. From search_accounts."
},
"customer_id": {
"type": "string",
"description": "Customer to budget against. Look it up with search_customers."
},
"department_id": {
"type": "string",
"description": "Department/location to budget against."
}
}
},
"description": "Explicit lines. Use this OR accounts OR spread, never more than one."
},
"spread": {
"type": "array",
"items": {
"type": "object",
"required": [
"account_id",
"annual_amount"
],
"properties": {
"class_id": {
"type": "string",
"description": "Class to budget against. Look it up with search_classes."
},
"account_id": {
"type": "string",
"description": "Account being budgeted."
},
"customer_id": {
"type": "string",
"description": "Customer to budget against. Look it up with search_customers."
},
"annual_amount": {
"type": "number",
"description": "Total for the whole budget window, divided evenly across its periods."
},
"department_id": {
"type": "string",
"description": "Department/location to budget against."
}
}
},
"description": "A single total per account, spread evenly. Where it does not divide exactly, the FINAL period absorbs the remainder and the result says so."
},
"dry_run": {
"type": "boolean",
"description": "Return what would be written, and write nothing. Re-run the identical call without it to apply."
},
"accounts": {
"type": "array",
"items": {
"type": "object",
"required": [
"account_id",
"amounts"
],
"properties": {
"amounts": {
"type": "array",
"items": {
"type": "number"
},
"description": "One amount per period, in order, matching the number of periods between start_date and end_date."
},
"class_id": {
"type": "string",
"description": "Class to budget against. Look it up with search_classes."
},
"account_id": {
"type": "string",
"description": "Account being budgeted."
},
"customer_id": {
"type": "string",
"description": "Customer to budget against. Look it up with search_customers."
},
"department_id": {
"type": "string",
"description": "Department/location to budget against."
}
}
},
"description": "One row per account carrying every period's amount in order — the shape a budget spreadsheet or CSV already has."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day the budget covers (YYYY-MM-DD)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"entry_type": {
"enum": [
"Monthly",
"Quarterly",
"Yearly"
],
"type": "string",
"description": "Period grain: Monthly (default), Quarterly or Yearly. These are the only three QuickBooks accepts."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day the budget covers (YYYY-MM-DD). It does NOT have to align to the fiscal year."
},
"budget_type": {
"type": "string",
"description": "Leave unset. Only profit-and-loss budgets can be created through the API; anything else is refused rather than silently downgraded."
}
}
}
}
},
"annotations": {
"title": "Create Budget",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Change a budget in QuickBooks Online: rename it, move its window, or set amounts on its lines. Requires budget_id and the sync_token from get_budget. HOW LINES BEHAVE, because it is not what most APIs do. Lines MERGE by (period, account, dimension): a line you send replaces the matching one, and every line you do NOT send is left exactly as it was. A line can be set to 0, but it CANNOT be removed — QuickBooks has no delete for a budget line, and sending an empty list does nothing at all. The only way to remove lines is delete_budget, which removes the whole budget. So: to correct an amount, send that line. To empty a line, send it with amount 0 and it will remain on the budget showing zero. To remove a line that should never have existed, the budget has to be rebuilt. Lines can be given as explicit `lines`, as `accounts` (one array of amounts per account in period order), or as `spread` (an annual figure divided across the periods). Pass dry_run: true to see what would change, including how many existing lines would be left alone, without writing. Xero budgets cannot be changed through its API — the endpoint is GET-only; edit those in Xero itself.
The description explains the capability, when to use it, and what to expect.
Inputs89/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › budget_id
The budget's id, from search_budgets or get_budget.
Clear enough to supply this argument.
params › sync_token
The sync_token from get_budget. Required: QuickBooks rejects an absent token exactly as it rejects a stale one, because both mean the budget may have changed since you read it.
Clear enough to supply this argument.
params › name
New name. The existing name is sent automatically when this is omitted — QuickBooks refuses an update that carries no name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
New first day of the budget window.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
New last day of the budget window.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › lines › items › date
First day of the period this amount belongs to.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › lines › items › account_id
Account being budgeted.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › lines › items › amount
New amount. 0 zeroes the line; it stays on the budget.
Clear enough to supply this argument.
params › lines › items › class_id
Class this line is budgeted against.
Clear enough to supply this argument.
params › lines › items › customer_id
Customer this line is budgeted against.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › lines › items › department_id
Department/location this line is budgeted against.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › accounts › items › account_id
Account being budgeted.
Clear enough to supply this argument.
params › accounts › items › amounts
One amount per period, in order, across the budget's window.
Clear enough to supply this argument.
params › accounts › items › class_id
Class this line is budgeted against.
Clear enough to supply this argument.
params › accounts › items › customer_id
Customer this line is budgeted against.
Clear enough to supply this argument.
params › accounts › items › department_id
Department/location this line is budgeted against.
Clear enough to supply this argument.
params › spread › items › account_id
Account being budgeted.
Clear enough to supply this argument.
params › spread › items › annual_amount
Total across the budget window, divided evenly across its periods.
Clear enough to supply this argument.
params › spread › items › class_id
Class this line is budgeted against.
Clear enough to supply this argument.
params › spread › items › customer_id
Customer this line is budgeted against.
Clear enough to supply this argument.
params › spread › items › department_id
Department/location this line is budgeted against.
Clear enough to supply this argument.
params › dry_run
Report what would change and write nothing.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_budget",
"title": "Update Budget",
"description": "Change a budget in QuickBooks Online: rename it, move its window, or set amounts on its lines. Requires budget_id and the sync_token from get_budget. HOW LINES BEHAVE, because it is not what most APIs do. Lines MERGE by (period, account, dimension): a line you send replaces the matching one, and every line you do NOT send is left exactly as it was. A line can be set to 0, but it CANNOT be removed — QuickBooks has no delete for a budget line, and sending an empty list does nothing at all. The only way to remove lines is delete_budget, which removes the whole budget. So: to correct an amount, send that line. To empty a line, send it with amount 0 and it will remain on the budget showing zero. To remove a line that should never have existed, the budget has to be rebuilt. Lines can be given as explicit `lines`, as `accounts` (one array of amounts per account in period order), or as `spread` (an annual figure divided across the periods). Pass dry_run: true to see what would change, including how many existing lines would be left alone, without writing. Xero budgets cannot be changed through its API — the endpoint is GET-only; edit those in Xero itself.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"budget_id",
"sync_token",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "New name. The existing name is sent automatically when this is omitted — QuickBooks refuses an update that carries no name."
},
"lines": {
"type": "array",
"items": {
"type": "object",
"required": [
"date",
"account_id",
"amount"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day of the period this amount belongs to."
},
"amount": {
"type": "number",
"description": "New amount. 0 zeroes the line; it stays on the budget."
},
"class_id": {
"type": "string",
"description": "Class this line is budgeted against."
},
"account_id": {
"type": "string",
"description": "Account being budgeted."
},
"customer_id": {
"type": "string",
"description": "Customer this line is budgeted against."
},
"department_id": {
"type": "string",
"description": "Department/location this line is budgeted against."
}
}
},
"description": "Explicit lines to set. Use this OR accounts OR spread."
},
"spread": {
"type": "array",
"items": {
"type": "object",
"required": [
"account_id",
"annual_amount"
],
"properties": {
"class_id": {
"type": "string",
"description": "Class this line is budgeted against."
},
"account_id": {
"type": "string",
"description": "Account being budgeted."
},
"customer_id": {
"type": "string",
"description": "Customer this line is budgeted against."
},
"annual_amount": {
"type": "number",
"description": "Total across the budget window, divided evenly across its periods."
},
"department_id": {
"type": "string",
"description": "Department/location this line is budgeted against."
}
}
},
"description": "A single total per account, spread evenly. The final period absorbs any rounding remainder, and the result says so."
},
"dry_run": {
"type": "boolean",
"description": "Report what would change and write nothing."
},
"accounts": {
"type": "array",
"items": {
"type": "object",
"required": [
"account_id",
"amounts"
],
"properties": {
"amounts": {
"type": "array",
"items": {
"type": "number"
},
"description": "One amount per period, in order, across the budget's window."
},
"class_id": {
"type": "string",
"description": "Class this line is budgeted against."
},
"account_id": {
"type": "string",
"description": "Account being budgeted."
},
"customer_id": {
"type": "string",
"description": "Customer this line is budgeted against."
},
"department_id": {
"type": "string",
"description": "Department/location this line is budgeted against."
}
}
},
"description": "One row per account carrying every period's amount in order."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "New last day of the budget window."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"budget_id": {
"type": "string",
"description": "The budget's id, from search_budgets or get_budget."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "New first day of the budget window."
},
"sync_token": {
"type": "string",
"description": "The sync_token from get_budget. Required: QuickBooks rejects an absent token exactly as it rejects a stale one, because both mean the budget may have changed since you read it."
}
}
}
}
},
"annotations": {
"title": "Update Budget",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Delete a budget from QuickBooks Online, with all of its lines. Pass confirm: true on the SAME call to go ahead — a first call without it reports what the budget contains and writes nothing, so nobody has to delete something to find out what was in it. Why it asks at all, when almost nothing else here does: the API has no undo for this, and budget lines cannot be removed individually, so a budget deleted by mistake has to be typed in again from scratch. The response carries the full contents of what was deleted, which is the only copy. To empty a budget without deleting it, set its lines to 0 with update_budget instead — they stay on the budget showing zero. Xero budgets cannot be deleted through its API; remove those in Xero itself.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › budget_id
The budget's id, from search_budgets.
Clear enough to supply this argument.
params › confirm
Set true to delete. Without it the tool reports the budget's name, window and line count and deletes nothing.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_budget",
"title": "Delete Budget",
"description": "Delete a budget from QuickBooks Online, with all of its lines. Pass confirm: true on the SAME call to go ahead — a first call without it reports what the budget contains and writes nothing, so nobody has to delete something to find out what was in it. Why it asks at all, when almost nothing else here does: the API has no undo for this, and budget lines cannot be removed individually, so a budget deleted by mistake has to be typed in again from scratch. The response carries the full contents of what was deleted, which is the only copy. To empty a budget without deleting it, set its lines to 0 with update_budget instead — they stay on the budget showing zero. Xero budgets cannot be deleted through its API; remove those in Xero itself.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"budget_id",
"realm_id"
],
"properties": {
"confirm": {
"type": "boolean",
"description": "Set true to delete. Without it the tool reports the budget's name, window and line count and deletes nothing."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"budget_id": {
"type": "string",
"description": "The budget's id, from search_budgets."
}
}
}
}
},
"annotations": {
"title": "Delete Budget",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Compare a budget against what actually happened, on QuickBooks Online or Xero. Returns one row per account per period with budget, actual, variance and variance percent, plus whether the variance is favourable — above budget is favourable for income and unfavourable for expense, taken from each account's own classification rather than from the row's label. Rows cover every account with a budget figure OR actual activity in the window, so unbudgeted spend appears rather than being hidden by the budget's own shape. Name the budget with budget_id (from search_budgets) or budget_name. If neither is given, a budget whose dates cannot overlap the period is ignored; if exactly one remains it is used and the notes say so, and if several remain the tool lists them with their ids instead of picking one.This is built from the budget and the profit-and-loss rather than from QuickBooks' own Budget vs Actuals report, which cannot be pointed at a particular budget and has no period columns. Despite the qbo_ prefix it serves Xero organisations too.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › budget_id
Which budget to report on, from search_budgets.
Clear enough to supply this argument.
params › budget_name
Name, or part of a name, of the budget to report on. Use budget_id when you have it.
Clear enough to supply this argument.
params › start_date
Start of the period to report (YYYY-MM-DD). Defaults to the budget's own start.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
End of the period to report (YYYY-MM-DD). Defaults to the budget's own end.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › summarize_by
Period grain for the comparison. Month (default), Quarter, or Total for one column across the whole window.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_budget_vs_actuals",
"title": "Report Budget Vs Actuals",
"description": "Compare a budget against what actually happened, on QuickBooks Online or Xero. Returns one row per account per period with budget, actual, variance and variance percent, plus whether the variance is favourable — above budget is favourable for income and unfavourable for expense, taken from each account's own classification rather than from the row's label. Rows cover every account with a budget figure OR actual activity in the window, so unbudgeted spend appears rather than being hidden by the budget's own shape. Name the budget with budget_id (from search_budgets) or budget_name. If neither is given, a budget whose dates cannot overlap the period is ignored; if exactly one remains it is used and the notes say so, and if several remain the tool lists them with their ids instead of picking one.This is built from the budget and the profit-and-loss rather than from QuickBooks' own Budget vs Actuals report, which cannot be pointed at a particular budget and has no period columns. Despite the qbo_ prefix it serves Xero organisations too.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "End of the period to report (YYYY-MM-DD). Defaults to the budget's own end."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"budget_id": {
"type": "string",
"description": "Which budget to report on, from search_budgets."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start of the period to report (YYYY-MM-DD). Defaults to the budget's own start."
},
"budget_name": {
"type": "string",
"description": "Name, or part of a name, of the budget to report on. Use budget_id when you have it."
},
"summarize_by": {
"enum": [
"Month",
"Quarter",
"Total"
],
"type": "string",
"description": "Period grain for the comparison. Month (default), Quarter, or Total for one column across the whole window."
}
}
}
}
},
"annotations": {
"title": "Report Budget Vs Actuals",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Forward-looking revenue schedule for a QuickBooks Online Advanced company that uses automatic revenue recognition: the revenue still to be recognised, by customer and P&L income account, month by month until each contract is fully recognised. Use it for forward revenue, deferred revenue waterfalls and revenue backlog questions instead of assembling them from the general ledger. QuickBooks does not expose its recognition schedules, so this rebuilds them from what is posted: invoice lines under revenue recognition (billed) and the Revenue Recognition entries on the income accounts (recognised to date). What remains per invoice is exact; its spread over future months follows the rate each invoice is already recognising at, or the item's usual term for contracts that have not started (those rows are marked estimated). The result ties the total remaining to the deferred revenue liability balance and reports any difference. When tie_out.explained_by_unmatched is true, the whole difference is recognition posted against the invoice numbers in notes.unmatched_recognition, which match no deferred invoice line (typically an invoice edited after recognition started): present the schedule as correct for every other invoice and name those invoices for the user to check. Any other difference usually means older invoices are still open: widen invoices_since. Do not look for the liability by its Deferred Revenue subtype: automatic recognition often posts to an account without it, and this tool finds the right one from the invoices. Not available for Xero, which has no automatic revenue recognition.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › as_of
Schedule date (YYYY-MM-DD). Recognition posted on or before it counts as done. Default: today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › horizon_months
Months shown individually from the as_of month (e.g. 36 or 60). Anything later is summed into beyond_horizon, so totals still tie. Default: 60.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › detail
'customer' (default): one row per customer and income account. 'invoice': one row per invoice as well, for drilling into a customer.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › invoices_since
Earliest invoice date to include (YYYY-MM-DD). Default: three years before as_of. Widen it if the tie-out shows a difference.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_deferred_revenue_schedule",
"title": "Report Deferred Revenue Schedule",
"description": "Forward-looking revenue schedule for a QuickBooks Online Advanced company that uses automatic revenue recognition: the revenue still to be recognised, by customer and P&L income account, month by month until each contract is fully recognised. Use it for forward revenue, deferred revenue waterfalls and revenue backlog questions instead of assembling them from the general ledger. QuickBooks does not expose its recognition schedules, so this rebuilds them from what is posted: invoice lines under revenue recognition (billed) and the Revenue Recognition entries on the income accounts (recognised to date). What remains per invoice is exact; its spread over future months follows the rate each invoice is already recognising at, or the item's usual term for contracts that have not started (those rows are marked estimated). The result ties the total remaining to the deferred revenue liability balance and reports any difference. When tie_out.explained_by_unmatched is true, the whole difference is recognition posted against the invoice numbers in notes.unmatched_recognition, which match no deferred invoice line (typically an invoice edited after recognition started): present the schedule as correct for every other invoice and name those invoices for the user to check. Any other difference usually means older invoices are still open: widen invoices_since. Do not look for the liability by its Deferred Revenue subtype: automatic recognition often posts to an account without it, and this tool finds the right one from the invoices. Not available for Xero, which has no automatic revenue recognition.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"as_of": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Schedule date (YYYY-MM-DD). Recognition posted on or before it counts as done. Default: today."
},
"detail": {
"enum": [
"customer",
"invoice"
],
"type": "string",
"description": "'customer' (default): one row per customer and income account. 'invoice': one row per invoice as well, for drilling into a customer."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"horizon_months": {
"type": "integer",
"maximum": 120,
"minimum": 1,
"description": "Months shown individually from the as_of month (e.g. 36 or 60). Anything later is summed into beyond_horizon, so totals still tie. Default: 60."
},
"invoices_since": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Earliest invoice date to include (YYYY-MM-DD). Default: three years before as_of. Widen it if the tie-out shows a difference."
}
}
}
}
},
"annotations": {
"title": "Report Deferred Revenue Schedule",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Pull the Statement of Cash Flows from QBO. Returns structured JSON with operating, investing and financing activities. Use for any question about where the cash went, cash burn, or runway - on accrual books the profit and loss cannot answer those, because a company can be profitable and still running out of money. Internal working data for Claude's analysis - not displayed to users. Not available for Xero companies: Xero does not offer a cash flow statement through its reports API.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Period start in YYYY-MM-DD format.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Period end in YYYY-MM-DD format. Default: today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › accounting_method
Accounting method. Default: company preference.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › summarize_column_by
Column grouping. Use Month for a trend rather than a single figure.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_cash_flow",
"title": "Cash Flow Statement",
"description": "Pull the Statement of Cash Flows from QBO. Returns structured JSON with operating, investing and financing activities. Use for any question about where the cash went, cash burn, or runway - on accrual books the profit and loss cannot answer those, because a company can be profitable and still running out of money. Internal working data for Claude's analysis - not displayed to users. Not available for Xero companies: Xero does not offer a cash flow statement through its reports API.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end in YYYY-MM-DD format. Default: today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start in YYYY-MM-DD format."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference."
},
"summarize_column_by": {
"enum": [
"Total",
"Month",
"Quarter",
"Year"
],
"type": "string",
"description": "Column grouping. Use Month for a trend rather than a single figure."
}
}
}
}
},
"annotations": {
"title": "Cash Flow Statement",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Pull a flat transaction listing from QBO for a period, optionally grouped by vendor, by customer, or split out line by line. Prefer this over qbo_report_general_ledger for questions like what did we spend with a vendor, what has this customer been billed, or show me every transaction in this range - the GL answers them too but returns far more data for the same question. Filtering by vendor or customer takes a QuickBooks Id, not a name - use search_vendors or search_customers to get one. This report cannot filter by class or by account - QuickBooks ignores both parameters here, unlike on the P and L, the balance sheet and the general ledger. For a class-scoped or account-scoped question use qbo_report_general_ledger. Set include_cleared_status to see which rows are already reconciled - that column is the only place QuickBooks reports it. Internal working data for Claude's analysis - not displayed to users. Not available for Xero companies: Xero has no transaction-list report. Read the per-document search tools one month or quarter at a time instead (the list is in qbo_report_general_ledger's description), not with fetchAll.
The description explains the capability, when to use it, and what to expect.
Inputs72/100
6 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › start_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › end_date
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounting_method
Accounting method. Default: company preference.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › group_by
How to group. 'none' is a flat list; 'vendor' and 'customer' group by entity; 'splits' shows each line of a transaction rather than only the document total. Default: none.
Clear enough to supply this argument.
params › vendor
Restrict to one vendor, by QuickBooks Id. NOT a name - search_vendors returns the Id.
Clear enough to supply this argument.
params › customer
Restrict to one customer, by QuickBooks Id. NOT a name - search_customers returns the Id.
Clear enough to supply this argument.
params › include_cleared_status
Add the reconciliation column (QuickBooks calls it Clr) to each row, and lose the Posting column - QuickBooks will not return both. R means reconciled, C means cleared but not yet reconciled, and empty means neither - non-bank documents like bills, invoices and credit memos never carry a value at all. Use it to see which transactions are already reconciled BEFORE editing or deleting them: QuickBooks reports this nowhere else, not on the transaction itself. Default: false.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_transaction_list",
"title": "Transaction List",
"description": "Pull a flat transaction listing from QBO for a period, optionally grouped by vendor, by customer, or split out line by line. Prefer this over qbo_report_general_ledger for questions like what did we spend with a vendor, what has this customer been billed, or show me every transaction in this range - the GL answers them too but returns far more data for the same question. Filtering by vendor or customer takes a QuickBooks Id, not a name - use search_vendors or search_customers to get one. This report cannot filter by class or by account - QuickBooks ignores both parameters here, unlike on the P and L, the balance sheet and the general ledger. For a class-scoped or account-scoped question use qbo_report_general_ledger. Set include_cleared_status to see which rows are already reconciled - that column is the only place QuickBooks reports it. Internal working data for Claude's analysis - not displayed to users. Not available for Xero companies: Xero has no transaction-list report. Read the per-document search tools one month or quarter at a time instead (the list is in qbo_report_general_ledger's description), not with fetchAll.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"vendor": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"maxLength": 20,
"description": "Restrict to one vendor, by QuickBooks Id. NOT a name - search_vendors returns the Id."
},
"customer": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"maxLength": 20,
"description": "Restrict to one customer, by QuickBooks Id. NOT a name - search_customers returns the Id."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"group_by": {
"enum": [
"none",
"vendor",
"customer",
"splits"
],
"type": "string",
"description": "How to group. 'none' is a flat list; 'vendor' and 'customer' group by entity; 'splits' shows each line of a transaction rather than only the document total. Default: none."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference."
},
"include_cleared_status": {
"type": "boolean",
"description": "Add the reconciliation column (QuickBooks calls it Clr) to each row, and lose the Posting column - QuickBooks will not return both. R means reconciled, C means cleared but not yet reconciled, and empty means neither - non-bank documents like bills, invoices and credit memos never carry a value at all. Use it to see which transactions are already reconciled BEFORE editing or deleting them: QuickBooks reports this nowhere else, not on the transaction itself. Default: false."
}
}
}
}
},
"annotations": {
"title": "Transaction List",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Pull the General Ledger Detail report from QBO. Returns every transaction for all or specific accounts in the period. Use the account param to filter to a specific account and class_id to filter to a single class. Use max_rows to limit response size for large datasets. Internal working data for Claude's analysis. Not available for Xero companies. For a Xero account's activity, read the documents one month or quarter at a time (bills, vendor credits, spend money via search_purchases, receive money via search_sales_receipts, invoices, credit notes, manual journals; search_bank_transactions for a bank account) and compare the total with qbo_report_trial_balance.
The description explains the capability, when to use it, and what to expect.
Inputs86/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Period start in YYYY-MM-DD format. Default: start of current fiscal year.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Period end in YYYY-MM-DD format. Default: today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › accounting_method
Accounting method. Default: company preference.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › account
Filter to a specific account by QBO account ID. Omit to return all accounts.
Clear enough to supply this argument.
params › class_id
Filter to a single class by ID. Look it up with search_classes. Omit for all classes.
Clear enough to supply this argument.
params › max_rows
Maximum rows to return. Default: unlimited. Use to limit response size for large GL reports. Max: 5000.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_general_ledger",
"title": "General Ledger",
"description": "Pull the General Ledger Detail report from QBO. Returns every transaction for all or specific accounts in the period. Use the account param to filter to a specific account and class_id to filter to a single class. Use max_rows to limit response size for large datasets. Internal working data for Claude's analysis. Not available for Xero companies. For a Xero account's activity, read the documents one month or quarter at a time (bills, vendor credits, spend money via search_purchases, receive money via search_sales_receipts, invoices, credit notes, manual journals; search_bank_transactions for a bank account) and compare the total with qbo_report_trial_balance.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"account": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Filter to a specific account by QBO account ID. Omit to return all accounts."
},
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Filter to a single class by ID. Look it up with search_classes. Omit for all classes."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end in YYYY-MM-DD format. Default: today."
},
"max_rows": {
"type": "integer",
"maximum": 5000,
"description": "Maximum rows to return. Default: unlimited. Use to limit response size for large GL reports. Max: 5000.",
"exclusiveMinimum": 0
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start in YYYY-MM-DD format. Default: start of current fiscal year."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference."
}
}
}
}
},
"annotations": {
"title": "General Ledger",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Pull Profit and Loss broken down by Class from QBO. Returns revenue, expenses and net income with one column per class, plus a Not Specified column for anything unclassed - which is the fastest way to spot transactions that missed a class. Use this to compare profitability across profit centers, projects or service lines. Optionally filter to a single class.On Xero this is ProfitAndLoss broken down by a TRACKING CATEGORY, and the meaning of class_id changes with it: QuickBooks filters the report to one class, while Xero groups the report BY a category so its options become the columns. Pass a Xero tracking category name or id (or omit it to use the organisation's first); a QuickBooks class id is refused with the list of what the organisation actually has. Xero allows only two tracking categories in total, which is why create_department is refused there rather than consuming the second slot.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Period start in YYYY-MM-DD format. Default: start of current fiscal year.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Period end in YYYY-MM-DD format. Default: today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › accounting_method
Accounting method. Default: company preference.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › class_id
Filter to a single class by ID. Omit to see all classes side by side.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Profit and Loss by Class",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_report_profit_and_loss_by_class",
"title": "Profit and Loss by Class",
"description": "Pull Profit and Loss broken down by Class from QBO. Returns revenue, expenses and net income with one column per class, plus a Not Specified column for anything unclassed - which is the fastest way to spot transactions that missed a class. Use this to compare profitability across profit centers, projects or service lines. Optionally filter to a single class.On Xero this is ProfitAndLoss broken down by a TRACKING CATEGORY, and the meaning of class_id changes with it: QuickBooks filters the report to one class, while Xero groups the report BY a category so its options become the columns. Pass a Xero tracking category name or id (or omit it to use the organisation's first); a QuickBooks class id is refused with the list of what the organisation actually has. Xero allows only two tracking categories in total, which is why create_department is refused there rather than consuming the second slot.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"maxLength": 50,
"description": "Filter to a single class by ID. Omit to see all classes side by side."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period end in YYYY-MM-DD format. Default: today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Period start in YYYY-MM-DD format. Default: start of current fiscal year."
},
"accounting_method": {
"enum": [
"Cash",
"Accrual"
],
"type": "string",
"description": "Accounting method. Default: company preference."
}
}
}
}
},
"annotations": {
"title": "Profit and Loss by Class",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Read bank and credit card activity from the QuickBooks register: transactions already posted to the account, covering Purchases, Deposits, Transfers, Bill Payments, Payments and Journal Entries. ALWAYS use this to answer a question about what is on a bank or credit card account - what was spent, what came in, what a vendor was paid, what is on the account this month - whether or not the company also has a bank feed connected. A connected bank feed is for BOOKING new activity into the books, not for answering questions; unbooked feed rows are not the client's books. It is NOT a bank feed: it shows what has been entered into QuickBooks, so anything not yet recorded does not appear and its absence is not evidence it did not happen - say which source you used. QuickBooks own For Review queue of downloaded but uncategorized items is not available through the public QuickBooks API, so it cannot be read here; it can be seen in the QuickBooks UI, and Intuit's own QuickBooks Labs connector can read it. Also use it before booking a bank line, to check the same transaction was not already posted by another route. Pass a date range: the four types QuickBooks cannot filter by account server-side are fetched by date and filtered here.On Xero there is no register endpoint at all, so this RECONSTRUCTS the account's movements from the endpoints Xero does expose and reconciles the total against Xero's own bank summary. On Xero, ask for a quarter at a time, or a month for a busy account: one call reads at most 10,000 spend and receive transactions on the account (and as many payments) in its range, and a range holding more is refused at once with its count, not cut short. When a period does not tie to that summary - typically a Receipt or Expense Claim, which Xero does not let this connector read - the rows that CAN be read are returned with a `warning` stating both totals and the difference. That list is INCOMPLETE: tell the user the gap before using it to reconcile or as a duplicate check, and let them decide (narrowing to single months shows which month the missing item is in). `amount` is SIGNED on both ledgers: money out of the account is negative, money in is positive. On Xero sync_token comes back empty (Xero has none) and category, class and payment method are null, because a Xero register does not carry the other side of the entry. Each row carries linked_txn, the documents it is joined to at DOCUMENT level as "<Type> <id>" - a payment that has been banked shows "Deposit <id>", which is how you find the deposit a payment sits on when QuickBooks refuses to change it (code 6540). Empty on Xero and on anything with no links. Customer payments NOT YET BANKED are found by passing the Undeposited Funds account (AccountSubType UndepositedFunds, from search_accounts) as account_id: QuickBooks records such a payment against that account until it is put on a deposit.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › account_id
QBO Bank Account ID to search (required). Get from search_accounts. The Undeposited Funds account works too: it lists the customer payments received but not yet banked.
Clear enough to supply this argument.
params › start_date
Filter start date (YYYY-MM-DD). Default: no lower bound on QuickBooks; 1 January of the current year on Xero, where a quarter or a month at a time is the range to ask for.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Filter end date (YYYY-MM-DD). Default: no upper bound on QuickBooks; today on Xero.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › include_deposits
Include deposits into this account. Default: true.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_bank_transactions",
"title": "Search Bank Transactions",
"description": "Read bank and credit card activity from the QuickBooks register: transactions already posted to the account, covering Purchases, Deposits, Transfers, Bill Payments, Payments and Journal Entries. ALWAYS use this to answer a question about what is on a bank or credit card account - what was spent, what came in, what a vendor was paid, what is on the account this month - whether or not the company also has a bank feed connected. A connected bank feed is for BOOKING new activity into the books, not for answering questions; unbooked feed rows are not the client's books. It is NOT a bank feed: it shows what has been entered into QuickBooks, so anything not yet recorded does not appear and its absence is not evidence it did not happen - say which source you used. QuickBooks own For Review queue of downloaded but uncategorized items is not available through the public QuickBooks API, so it cannot be read here; it can be seen in the QuickBooks UI, and Intuit's own QuickBooks Labs connector can read it. Also use it before booking a bank line, to check the same transaction was not already posted by another route. Pass a date range: the four types QuickBooks cannot filter by account server-side are fetched by date and filtered here.On Xero there is no register endpoint at all, so this RECONSTRUCTS the account's movements from the endpoints Xero does expose and reconciles the total against Xero's own bank summary. On Xero, ask for a quarter at a time, or a month for a busy account: one call reads at most 10,000 spend and receive transactions on the account (and as many payments) in its range, and a range holding more is refused at once with its count, not cut short. When a period does not tie to that summary - typically a Receipt or Expense Claim, which Xero does not let this connector read - the rows that CAN be read are returned with a `warning` stating both totals and the difference. That list is INCOMPLETE: tell the user the gap before using it to reconcile or as a duplicate check, and let them decide (narrowing to single months shows which month the missing item is in). `amount` is SIGNED on both ledgers: money out of the account is negative, money in is positive. On Xero sync_token comes back empty (Xero has none) and category, class and payment method are null, because a Xero register does not carry the other side of the entry. Each row carries linked_txn, the documents it is joined to at DOCUMENT level as \"<Type> <id>\" - a payment that has been banked shows \"Deposit <id>\", which is how you find the deposit a payment sits on when QuickBooks refuses to change it (code 6540). Empty on Xero and on anything with no links. Customer payments NOT YET BANKED are found by passing the Undeposited Funds account (AccountSubType UndepositedFunds, from search_accounts) as account_id: QuickBooks records such a payment against that account until it is put on a deposit.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"account_id",
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Filter end date (YYYY-MM-DD). Default: no upper bound on QuickBooks; today on Xero."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"maxLength": 50,
"description": "QBO Bank Account ID to search (required). Get from search_accounts. The Undeposited Funds account works too: it lists the customer payments received but not yet banked."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Filter start date (YYYY-MM-DD). Default: no lower bound on QuickBooks; 1 January of the current year on Xero, where a quarter or a month at a time is the range to ask for."
},
"include_deposits": {
"type": "boolean",
"description": "Include deposits into this account. Default: true."
}
}
}
}
},
"annotations": {
"title": "Search Bank Transactions",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Generate a firm-branded Board Report PDF. Call this AFTER analysing the period. Provide the client name, period_start and period_end, cash position, and your analysis (summary, highlights, flags, recommendations). The server reads revenue, cost of sales and net income from the ledger's Profit and Loss for the period, and total assets, liabilities and equity from its Balance Sheet as at period_end (QuickBooks Online or Xero), and prints those, not typed figures. Net income is the ledger's own total (it includes cost of sales and other income and expense); total expenses is revenue minus net income. A supplied figure that disagrees is noted in the PDF and returned as a warning to tell the user, as is assets not equal to liabilities + equity. If the ledger cannot be read or the period is missing, supplied figures are printed marked "not verified against the ledger". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › client_name
Client/company name
Clear enough to supply this argument.
params › period_label
Period description, e.g. 'Q1 2026 (Jan-Mar)' or 'March 2026'
Clear enough to supply this argument.
params › period_start
First day of the period, YYYY-MM-DD. With period_end, the server reads the P&L for the period.
Clear enough to supply this argument.
params › period_end
Last day of the period, YYYY-MM-DD. The server reads the Balance Sheet as at this date.
Clear enough to supply this argument.
params › total_revenue
Optional. Total revenue (income) for the period
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › total_expenses
Optional. Revenue minus net income: cost of sales, expenses and other items, net
Clear enough to supply this argument.
params › net_income
Optional. Net income (or loss if negative) for the period
Clear enough to supply this argument.
params › total_assets
Optional. Total assets from Balance Sheet
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › total_liabilities
Optional. Total liabilities from Balance Sheet
Clear enough to supply this argument.
params › total_equity
Optional. Total equity from Balance Sheet
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › cash_position
Total cash and cash equivalents
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › gross_margin_pct
Gross margin percentage
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › burn_rate_monthly
Estimated monthly burn rate
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › runway_months
Estimated runway in months
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › ar_total
Total accounts receivable
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › ar_overdue
AR overdue amount (>30 days)
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › ar_aging_summary
Brief narrative summary of AR aging
Clear enough to supply this argument.
params › ap_total
Total accounts payable
Clear enough to supply this argument.
params › ap_overdue
AP overdue amount (>30 days)
Clear enough to supply this argument.
params › executive_summary
2-3 sentence executive summary of the financial position
Clear enough to supply this argument.
params › key_highlights
3-5 key highlights or takeaways from the period
Explain the meaning of this value, not just its name.
params › risk_flags › items › title
Short flag title
Explain the meaning of this value, not just its name.
params › risk_flags › items › detail
Detailed explanation
Clear enough to supply this argument.
params › risk_flags › items › severity
Flag severity level
Clear enough to supply this argument.
params › recommendations
Actionable recommendations based on the analysis
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_generate_board_report",
"title": "Generate Board Report",
"description": "Generate a firm-branded Board Report PDF. Call this AFTER analysing the period. Provide the client name, period_start and period_end, cash position, and your analysis (summary, highlights, flags, recommendations). The server reads revenue, cost of sales and net income from the ledger's Profit and Loss for the period, and total assets, liabilities and equity from its Balance Sheet as at period_end (QuickBooks Online or Xero), and prints those, not typed figures. Net income is the ledger's own total (it includes cost of sales and other income and expense); total expenses is revenue minus net income. A supplied figure that disagrees is noted in the PDF and returned as a warning to tell the user, as is assets not equal to liabilities + equity. If the ledger cannot be read or the period is missing, supplied figures are printed marked \"not verified against the ledger\". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"client_name",
"period_label",
"cash_position",
"executive_summary",
"key_highlights",
"risk_flags",
"recommendations",
"realm_id"
],
"properties": {
"ap_total": {
"type": "number",
"description": "Total accounts payable"
},
"ar_total": {
"type": "number",
"description": "Total accounts receivable"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"ap_overdue": {
"type": "number",
"description": "AP overdue amount (>30 days)"
},
"ar_overdue": {
"type": "number",
"description": "AR overdue amount (>30 days)"
},
"net_income": {
"type": "number",
"description": "Optional. Net income (or loss if negative) for the period"
},
"period_end": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day of the period, YYYY-MM-DD. The server reads the Balance Sheet as at this date."
},
"risk_flags": {
"type": "array",
"items": {
"type": "object",
"required": [
"title",
"detail",
"severity"
],
"properties": {
"title": {
"type": "string",
"description": "Short flag title"
},
"detail": {
"type": "string",
"description": "Detailed explanation"
},
"severity": {
"enum": [
"info",
"warning",
"critical"
],
"type": "string",
"description": "Flag severity level"
}
}
},
"maxItems": 20,
"description": "Risk flags, anomalies, or items needing attention"
},
"client_name": {
"type": "string",
"maxLength": 200,
"description": "Client/company name"
},
"period_label": {
"type": "string",
"maxLength": 100,
"description": "Period description, e.g. 'Q1 2026 (Jan-Mar)' or 'March 2026'"
},
"period_start": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day of the period, YYYY-MM-DD. With period_end, the server reads the P&L for the period."
},
"total_assets": {
"type": "number",
"description": "Optional. Total assets from Balance Sheet"
},
"total_equity": {
"type": "number",
"description": "Optional. Total equity from Balance Sheet"
},
"cash_position": {
"type": "number",
"description": "Total cash and cash equivalents"
},
"runway_months": {
"type": "number",
"description": "Estimated runway in months"
},
"total_revenue": {
"type": "number",
"description": "Optional. Total revenue (income) for the period"
},
"key_highlights": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 20,
"description": "3-5 key highlights or takeaways from the period"
},
"total_expenses": {
"type": "number",
"description": "Optional. Revenue minus net income: cost of sales, expenses and other items, net"
},
"recommendations": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 20,
"description": "Actionable recommendations based on the analysis"
},
"ar_aging_summary": {
"type": "string",
"description": "Brief narrative summary of AR aging"
},
"gross_margin_pct": {
"type": "number",
"description": "Gross margin percentage"
},
"burn_rate_monthly": {
"type": "number",
"description": "Estimated monthly burn rate"
},
"executive_summary": {
"type": "string",
"maxLength": 5000,
"description": "2-3 sentence executive summary of the financial position"
},
"total_liabilities": {
"type": "number",
"description": "Optional. Total liabilities from Balance Sheet"
}
}
}
}
},
"annotations": {
"title": "Generate Board Report",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Generate a firm-branded Month-End Close Report PDF. Call this AFTER running the close checks. Provide period_end, close checks, open items, adjusting entries, and reconciliation notes. The server reads the Trial Balance debit and credit totals and the Balance Sheet totals (assets; liabilities + equity) as at period_end from the ledger (QuickBooks Online or Xero) and prints those, not typed figures; it decides BALANCED and TIED from them, to the cent. A supplied total or verdict that disagrees is corrected, noted in the PDF and returned as a warning to tell the user. If the ledger cannot be read or period_end is missing, supplied totals are printed marked "not verified against the ledger". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.
The description explains the capability, when to use it, and what to expect.
Inputs89/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › client_name
Client/company name
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › period_label
Period description, e.g. 'March 2026'
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › close_date
Close date in YYYY-MM-DD format
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › period_end
Last day of the period being closed, YYYY-MM-DD. The server reads the Trial Balance and Balance Sheet totals as at this date.
Clear enough to supply this argument.
params › tb_debits_total
Optional. Cross-checked against the ledger's Trial Balance; printed (marked not verified) only when the ledger cannot be read
Clear enough to supply this argument.
params › tb_credits_total
Optional. Cross-checked against the ledger's Trial Balance; printed (marked not verified) only when the ledger cannot be read
Clear enough to supply this argument.
params › tb_balanced
Optional. Cross-checked only: the report uses the totals
Explain the meaning of this value, not just its name.
params › bs_assets
Optional. Cross-checked against the ledger's Balance Sheet; printed (marked not verified) only when the ledger cannot be read
Clear enough to supply this argument.
params › bs_liabilities_equity
Optional. Cross-checked against the ledger's Balance Sheet; printed (marked not verified) only when the ledger cannot be read
Clear enough to supply this argument.
params › bs_balanced
Optional. Cross-checked only: the report uses the totals
Explain the meaning of this value, not just its name.
params › checklist › items › check
Name of the close check
Clear enough to supply this argument.
params › checklist › items › status
Check result
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › checklist › items › note
Brief note or explanation
Explain the meaning of this value, not just its name.
params › open_items › items › description
Description of the open item
Clear enough to supply this argument.
params › open_items › items › amount
Dollar amount
Clear enough to supply this argument.
params › open_items › items › age_days
Age in days if applicable
Clear enough to supply this argument.
params › reconciliation_notes
Notes from bank/account reconciliations
Clear enough to supply this argument.
params › adjusting_entries › items › account
Account name
Clear enough to supply this argument.
params › adjusting_entries › items › debit
Debit amount (0 if credit-only)
Clear enough to supply this argument.
params › adjusting_entries › items › credit
Credit amount (0 if debit-only)
Clear enough to supply this argument.
params › adjusting_entries › items › memo
Memo/explanation for the entry
Clear enough to supply this argument.
params › close_summary
2-3 sentence summary of the close status
Clear enough to supply this argument.
params › issues_found
Total issues found during close
Clear enough to supply this argument.
params › issues_resolved
Issues resolved during this close
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_generate_close_report",
"title": "Generate Close Report",
"description": "Generate a firm-branded Month-End Close Report PDF. Call this AFTER running the close checks. Provide period_end, close checks, open items, adjusting entries, and reconciliation notes. The server reads the Trial Balance debit and credit totals and the Balance Sheet totals (assets; liabilities + equity) as at period_end from the ledger (QuickBooks Online or Xero) and prints those, not typed figures; it decides BALANCED and TIED from them, to the cent. A supplied total or verdict that disagrees is corrected, noted in the PDF and returned as a warning to tell the user. If the ledger cannot be read or period_end is missing, supplied totals are printed marked \"not verified against the ledger\". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"client_name",
"period_label",
"close_date",
"checklist",
"open_items",
"reconciliation_notes",
"adjusting_entries",
"close_summary",
"issues_found",
"issues_resolved",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"bs_assets": {
"type": "number",
"description": "Optional. Cross-checked against the ledger's Balance Sheet; printed (marked not verified) only when the ledger cannot be read"
},
"checklist": {
"type": "array",
"items": {
"type": "object",
"required": [
"check",
"status",
"note"
],
"properties": {
"note": {
"type": "string",
"description": "Brief note or explanation"
},
"check": {
"type": "string",
"description": "Name of the close check"
},
"status": {
"enum": [
"pass",
"fail",
"warning",
"na"
],
"type": "string",
"description": "Check result"
}
}
},
"maxItems": 30,
"description": "List of close checks performed with results"
},
"close_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Close date in YYYY-MM-DD format"
},
"open_items": {
"type": "array",
"items": {
"type": "object",
"required": [
"description",
"amount"
],
"properties": {
"amount": {
"type": "number",
"description": "Dollar amount"
},
"age_days": {
"type": "number",
"description": "Age in days if applicable"
},
"description": {
"type": "string",
"description": "Description of the open item"
}
}
},
"maxItems": 50,
"description": "Outstanding items that need resolution"
},
"period_end": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day of the period being closed, YYYY-MM-DD. The server reads the Trial Balance and Balance Sheet totals as at this date."
},
"bs_balanced": {
"type": "boolean",
"description": "Optional. Cross-checked only: the report uses the totals"
},
"client_name": {
"type": "string",
"maxLength": 200,
"description": "Client/company name"
},
"tb_balanced": {
"type": "boolean",
"description": "Optional. Cross-checked only: the report uses the totals"
},
"issues_found": {
"type": "number",
"description": "Total issues found during close"
},
"period_label": {
"type": "string",
"maxLength": 100,
"description": "Period description, e.g. 'March 2026'"
},
"close_summary": {
"type": "string",
"maxLength": 5000,
"description": "2-3 sentence summary of the close status"
},
"issues_resolved": {
"type": "number",
"description": "Issues resolved during this close"
},
"tb_debits_total": {
"type": "number",
"description": "Optional. Cross-checked against the ledger's Trial Balance; printed (marked not verified) only when the ledger cannot be read"
},
"tb_credits_total": {
"type": "number",
"description": "Optional. Cross-checked against the ledger's Trial Balance; printed (marked not verified) only when the ledger cannot be read"
},
"adjusting_entries": {
"type": "array",
"items": {
"type": "object",
"required": [
"account",
"debit",
"credit",
"memo"
],
"properties": {
"memo": {
"type": "string",
"description": "Memo/explanation for the entry"
},
"debit": {
"type": "number",
"description": "Debit amount (0 if credit-only)"
},
"credit": {
"type": "number",
"description": "Credit amount (0 if debit-only)"
},
"account": {
"type": "string",
"description": "Account name"
}
}
},
"maxItems": 30,
"description": "Proposed adjusting journal entries"
},
"reconciliation_notes": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 20,
"description": "Notes from bank/account reconciliations"
},
"bs_liabilities_equity": {
"type": "number",
"description": "Optional. Cross-checked against the ledger's Balance Sheet; printed (marked not verified) only when the ledger cannot be read"
}
}
}
}
},
"annotations": {
"title": "Generate Close Report",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Generate a supporting memo PDF for a bookkeeping entry. Returns an attachment handle to pass straight to upload_attachable. Use this to document why an entry was made — every adjustment, reconciliation correction, or reclassification should have a supporting memo attached. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs89/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › client_name
Client/company name
Clear enough to supply this argument.
params › memo_title
Brief title for the memo (e.g. 'Bank Fee - March 2026 Service Charge')
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › memo_date
Date of the transaction in YYYY-MM-DD format
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › transaction_type
Type of QBO transaction (e.g. 'Purchase', 'Deposit', 'Transfer', 'Journal Entry')
Clear enough to supply this argument.
params › account_name
Account name the entry hits (e.g. 'Bank Charges & Fees')
Clear enough to supply this argument.
params › amount
Transaction amount
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › explanation
Detailed explanation of why this entry was made. Include calculation details if applicable.
Clear enough to supply this argument.
params › source_reference
Source documentation reference (e.g. 'Chase Bank Statement March 2026, Page 3, Line 14')
Clear enough to supply this argument.
params › prepared_by
Who prepared this memo. Default: the calling firm's name via Claude
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_generate_supporting_memo",
"title": "Generate Supporting Memo",
"description": "Generate a supporting memo PDF for a bookkeeping entry. Returns an attachment handle to pass straight to upload_attachable. Use this to document why an entry was made — every adjustment, reconciliation correction, or reclassification should have a supporting memo attached. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"client_name",
"memo_title",
"memo_date",
"transaction_type",
"account_name",
"amount",
"explanation",
"source_reference",
"realm_id"
],
"properties": {
"amount": {
"type": "number",
"description": "Transaction amount"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"memo_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Date of the transaction in YYYY-MM-DD format"
},
"memo_title": {
"type": "string",
"maxLength": 200,
"description": "Brief title for the memo (e.g. 'Bank Fee - March 2026 Service Charge')"
},
"client_name": {
"type": "string",
"description": "Client/company name"
},
"explanation": {
"type": "string",
"maxLength": 2000,
"description": "Detailed explanation of why this entry was made. Include calculation details if applicable."
},
"prepared_by": {
"type": "string",
"description": "Who prepared this memo. Default: the calling firm's name via Claude"
},
"account_name": {
"type": "string",
"description": "Account name the entry hits (e.g. 'Bank Charges & Fees')"
},
"source_reference": {
"type": "string",
"maxLength": 500,
"description": "Source documentation reference (e.g. 'Chase Bank Statement March 2026, Page 3, Line 14')"
},
"transaction_type": {
"type": "string",
"description": "Type of QBO transaction (e.g. 'Purchase', 'Deposit', 'Transfer', 'Journal Entry')"
}
}
}
}
},
"annotations": {
"title": "Generate Supporting Memo",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Generate a firm-branded Bank Reconciliation Report PDF. Call this AFTER comparing the ledger to the bank statement. Provide the statement ending date and balance, the bank_account_id, matched/unmatched transactions and notes. The server reads the GL balance of that account as at the statement ending date from the ledger (QuickBooks Online or Xero) and prints that, not a typed figure; it computes the difference (statement minus GL, to the cent), and the status reads RECONCILED only when it is zero. A supplied gl_ending_balance, difference or status that disagrees is corrected, noted in the PDF and returned as a warning to tell the user. If the ledger cannot be read or bank_account_id/statement_ending_date are missing, a supplied gl_ending_balance is printed marked "not verified against the ledger". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › client_name
Client/company name
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › period_label
Period description, e.g. 'March 2026'
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › bank_account_name
Name of the bank account being reconciled (e.g. 'Chase Business Checking')
Clear enough to supply this argument.
params › bank_account_id
Ledger id of the bank or credit-card account (QuickBooks Account Id or Xero AccountID). With statement_ending_date, the server reads the GL balance itself.
Clear enough to supply this argument.
params › statement_ending_date
Statement ending date, YYYY-MM-DD. The GL balance is read as at this date.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › statement_ending_balance
Ending balance per bank statement
Clear enough to supply this argument.
params › gl_ending_balance
Optional. The server reads the GL balance from the ledger when bank_account_id and statement_ending_date are given; a supplied value is cross-checked, and printed (marked not verified) only when the ledger cannot be read.
Clear enough to supply this argument.
params › difference
Optional. Difference between statement and GL (statement - GL). Cross-checked only: the report prints the server's statement - GL.
Clear enough to supply this argument.
params › matched_count
Number of transactions that matched between statement and GL
Proposed resolution (e.g. 'Record as Deposit', 'Void duplicate', 'Investigate')
Clear enough to supply this argument.
params › reconciliation_status
Optional. Your read of the result; RECONCILED is printed only when the difference is zero.
Clear enough to supply this argument.
params › notes
Reconciliation notes, observations, or next steps
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_generate_reconciliation_report",
"title": "Generate Reconciliation Report",
"description": "Generate a firm-branded Bank Reconciliation Report PDF. Call this AFTER comparing the ledger to the bank statement. Provide the statement ending date and balance, the bank_account_id, matched/unmatched transactions and notes. The server reads the GL balance of that account as at the statement ending date from the ledger (QuickBooks Online or Xero) and prints that, not a typed figure; it computes the difference (statement minus GL, to the cent), and the status reads RECONCILED only when it is zero. A supplied gl_ending_balance, difference or status that disagrees is corrected, noted in the PDF and returned as a warning to tell the user. If the ledger cannot be read or bank_account_id/statement_ending_date are missing, a supplied gl_ending_balance is printed marked \"not verified against the ledger\". Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"client_name",
"period_label",
"bank_account_name",
"statement_ending_balance",
"matched_count",
"matched_total",
"unmatched_statement_items",
"unmatched_gl_items",
"notes",
"realm_id"
],
"properties": {
"notes": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 30,
"description": "Reconciliation notes, observations, or next steps"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"difference": {
"type": "number",
"description": "Optional. Difference between statement and GL (statement - GL). Cross-checked only: the report prints the server's statement - GL."
},
"client_name": {
"type": "string",
"maxLength": 200,
"description": "Client/company name"
},
"period_label": {
"type": "string",
"maxLength": 100,
"description": "Period description, e.g. 'March 2026'"
},
"matched_count": {
"type": "number",
"description": "Number of transactions that matched between statement and GL"
},
"matched_total": {
"type": "number",
"description": "Total dollar amount of matched transactions"
},
"bank_account_id": {
"type": "string",
"maxLength": 100,
"description": "Ledger id of the bank or credit-card account (QuickBooks Account Id or Xero AccountID). With statement_ending_date, the server reads the GL balance itself."
},
"bank_account_name": {
"type": "string",
"maxLength": 200,
"description": "Name of the bank account being reconciled (e.g. 'Chase Business Checking')"
},
"gl_ending_balance": {
"type": "number",
"description": "Optional. The server reads the GL balance from the ledger when bank_account_id and statement_ending_date are given; a supplied value is cross-checked, and printed (marked not verified) only when the ledger cannot be read."
},
"unmatched_gl_items": {
"type": "array",
"items": {
"type": "object",
"required": [
"date",
"description",
"amount",
"proposed_action"
],
"properties": {
"date": {
"type": "string",
"description": "Transaction date (YYYY-MM-DD or human-readable)"
},
"amount": {
"type": "number",
"description": "Transaction amount"
},
"description": {
"type": "string",
"description": "Transaction description"
},
"proposed_action": {
"type": "string",
"description": "Proposed resolution (e.g. 'Record as Deposit', 'Void duplicate', 'Investigate')"
}
}
},
"maxItems": 100,
"description": "Items in GL not found on bank statement"
},
"reconciliation_status": {
"enum": [
"reconciled",
"unreconciled",
"partial"
],
"type": "string",
"description": "Optional. Your read of the result; RECONCILED is printed only when the difference is zero."
},
"statement_ending_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Statement ending date, YYYY-MM-DD. The GL balance is read as at this date."
},
"statement_ending_balance": {
"type": "number",
"description": "Ending balance per bank statement"
},
"unmatched_statement_items": {
"type": "array",
"items": {
"type": "object",
"required": [
"date",
"description",
"amount",
"proposed_action"
],
"properties": {
"date": {
"type": "string",
"description": "Transaction date (YYYY-MM-DD or human-readable)"
},
"amount": {
"type": "number",
"description": "Transaction amount"
},
"description": {
"type": "string",
"description": "Transaction description"
},
"proposed_action": {
"type": "string",
"description": "Proposed resolution (e.g. 'Record as Deposit', 'Void duplicate', 'Investigate')"
}
}
},
"maxItems": 100,
"description": "Items on bank statement not found in GL"
}
}
}
}
},
"annotations": {
"title": "Generate Reconciliation Report",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Generate a firm-branded Issues Report PDF. Call this AFTER pulling and analyzing GL, P&L, BS, AR/AP data from QBO report tools. Provide all issues found (miscategorizations, duplicates, missing entries, stale receivables/payables, unusual amounts, etc.) with severity levels and proposed actions. Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs84/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › client_name
Client/company name
Clear enough to supply this argument.
params › period_label
Period description, e.g. 'March 2026'
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › scan_date
Date the scan was performed in YYYY-MM-DD format
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › issues › items › category
Issue category
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › issues › items › severity
Issue severity
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › issues › items › description
Clear description of the issue found
Explain the meaning of this value, not just its name.
params › issues › items › account
Account name where the issue was found
Clear enough to supply this argument.
params › issues › items › amount
Dollar amount involved
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › issues › items › proposed_action
Proposed correction or next step
Clear enough to supply this argument.
params › issues › items › transaction_id
QBO transaction ID if applicable
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
Actionable recommendations based on the issues found
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "qbo_generate_issues_report",
"title": "Generate Issues Report",
"description": "Generate a firm-branded Issues Report PDF. Call this AFTER pulling and analyzing GL, P&L, BS, AR/AP data from QBO report tools. Provide all issues found (miscategorizations, duplicates, missing entries, stale receivables/payables, unusual amounts, etc.) with severity levels and proposed actions. Returns a signed download link (valid 24 hours) for the user, and an attachment handle (att_..., valid 1 hour) that upload_attachable accepts to attach the PDF to a QuickBooks or Xero transaction. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"client_name",
"period_label",
"scan_date",
"issues",
"summary_stats",
"recommendations",
"realm_id"
],
"properties": {
"issues": {
"type": "array",
"items": {
"type": "object",
"required": [
"category",
"severity",
"description",
"account",
"amount",
"proposed_action"
],
"properties": {
"amount": {
"type": "number",
"description": "Dollar amount involved"
},
"account": {
"type": "string",
"description": "Account name where the issue was found"
},
"category": {
"enum": [
"miscategorization",
"duplicate",
"missing",
"stale_receivable",
"stale_payable",
"personal_expense",
"unusual_amount",
"wrong_period"
],
"type": "string",
"description": "Issue category"
},
"severity": {
"enum": [
"info",
"warning",
"critical"
],
"type": "string",
"description": "Issue severity"
},
"description": {
"type": "string",
"description": "Clear description of the issue found"
},
"transaction_id": {
"type": "string",
"description": "QBO transaction ID if applicable"
},
"proposed_action": {
"type": "string",
"description": "Proposed correction or next step"
}
}
},
"maxItems": 100,
"description": "List of issues found during review"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"scan_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Date the scan was performed in YYYY-MM-DD format"
},
"client_name": {
"type": "string",
"description": "Client/company name"
},
"period_label": {
"type": "string",
"description": "Period description, e.g. 'March 2026'"
},
"summary_stats": {
"type": "object",
"required": [
"total_issues",
"by_severity",
"by_category"
],
"properties": {
"by_category": {
"type": "object",
"description": "Issue counts by category (e.g. { miscategorization: 3, duplicate: 1 })",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "number"
}
},
"by_severity": {
"type": "object",
"required": [
"info",
"warning",
"critical"
],
"properties": {
"info": {
"type": "number",
"description": "Count of info-level issues"
},
"warning": {
"type": "number",
"description": "Count of warning-level issues"
},
"critical": {
"type": "number",
"description": "Count of critical-level issues"
}
}
},
"total_issues": {
"type": "number",
"description": "Total issues found"
}
},
"description": "Summary statistics of all issues"
},
"recommendations": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 20,
"description": "Actionable recommendations based on the issues found"
}
}
}
}
},
"annotations": {
"title": "Generate Issues Report",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Read the NumbersGame company record for this realm: the Client Profile (company description, contacts, financial configuration), Open Items (triage notes), and Client-specific rules — all markdown. Read this before bookkeeping work to recall what's known about the company. Pass company_file_version, skill_version and skill_build, copied from this project's company .md file and from your installed skill, so NumbersGame can tell you whether the file in this project is still current and whether your skill is your firm's own package; if the reply carries context_update, relay it to the user in full and follow it — for a company it asks you to call get_company_file and replace the project's file. Note: this reads NumbersGame data only and does NOT touch QuickBooks — a success here does not confirm QBO connectivity. To verify QBO access, call a read tool such as search_accounts. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Input documentation gives an agent enough context to populate the arguments.
params › company_file_version
The number on the line 'NumbersGame context version: N' in this project's company .md file. Copy it exactly. OMIT this parameter if you cannot see that line — a guessed version is worse than none, because it is indistinguishable from a real one.
Clear enough to supply this argument.
params › skill_version
The version label of your installed NumbersGame Wizard skill, e.g. '2026.08.29.1', taken from the 'Skill version:' line in the skill. Omit it if you cannot see that line.
Clear enough to supply this argument.
params › skill_build
Which build of the NumbersGame skill you are running, copied exactly from the 'Skill build:' line in the skill: 'public', or 'firm:' followed by your firm's skill version (e.g. 'firm:3'). Omit it if you cannot see that line.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_company_profile",
"title": "Get Company Profile",
"description": "Read the NumbersGame company record for this realm: the Client Profile (company description, contacts, financial configuration), Open Items (triage notes), and Client-specific rules — all markdown. Read this before bookkeeping work to recall what's known about the company. Pass company_file_version, skill_version and skill_build, copied from this project's company .md file and from your installed skill, so NumbersGame can tell you whether the file in this project is still current and whether your skill is your firm's own package; if the reply carries context_update, relay it to the user in full and follow it — for a company it asks you to call get_company_file and replace the project's file. Note: this reads NumbersGame data only and does NOT touch QuickBooks — a success here does not confirm QBO connectivity. To verify QBO access, call a read tool such as search_accounts. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"skill_build": {
"type": "string",
"description": "Which build of the NumbersGame skill you are running, copied exactly from the 'Skill build:' line in the skill: 'public', or 'firm:' followed by your firm's skill version (e.g. 'firm:3'). Omit it if you cannot see that line."
},
"skill_version": {
"type": "string",
"maxLength": 64,
"description": "The version label of your installed NumbersGame Wizard skill, e.g. '2026.08.29.1', taken from the 'Skill version:' line in the skill. Omit it if you cannot see that line."
},
"company_file_version": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "The number on the line 'NumbersGame context version: N' in this project's company .md file. Copy it exactly. OMIT this parameter if you cannot see that line — a guessed version is worse than none, because it is indistinguishable from a real one."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Company Profile",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Get this company's NumbersGame setup file (.md) — the same file the portal's 'download company file' gives — so you can save it into the user's Claude Project knowledge for them. Use it when the user asks to set up this company in a project, or to update or refresh the company file, and when get_company_profile's context_update says the project's file is out of date. The reply is two blocks: how to save it, then the file itself. Save the file EXACTLY as returned, under the filename given, replacing any existing file of that name; never write or edit the file's content yourself, because its version line is how NumbersGame knows which instructions this project runs. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_company_file",
"title": "Get Company File",
"description": "Get this company's NumbersGame setup file (.md) — the same file the portal's 'download company file' gives — so you can save it into the user's Claude Project knowledge for them. Use it when the user asks to set up this company in a project, or to update or refresh the company file, and when get_company_profile's context_update says the project's file is out of date. The reply is two blocks: how to save it, then the file itself. Save the file EXACTLY as returned, under the filename given, replacing any existing file of that name; never write or edit the file's content yourself, because its version line is how NumbersGame knows which instructions this project runs. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Company File",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
List the companies you can use through this connection (a connection can be limited to chosen companies; connection_covers says which): each one's name, realm_id, ledger (QuickBooks or Xero) and whether the firm has set it to read-only. Call it when you need a realm_id and the project has no company file, instead of guessing one, then pass the realm_id it returns to the other tools. Takes no realm_id. The reply also carries setup advice for the user (a Claude Project per company with its company file, and onboarding); relay it once. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.
The description explains the capability, when to use it, and what to expect.
Inputs0/100
0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_companies",
"title": "List Companies",
"description": "List the companies you can use through this connection (a connection can be limited to chosen companies; connection_covers says which): each one's name, realm_id, ledger (QuickBooks or Xero) and whether the firm has set it to read-only. Call it when you need a realm_id and the project has no company file, instead of guessing one, then pass the realm_id it returns to the other tools. Takes no realm_id. The reply also carries setup advice for the user (a Claude Project per company with its company file, and onboarding); relay it once. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"properties": {},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Companies",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Search NumbersGame's own help: the step-by-step SOPs, help pages, example prompts and the NumbersGame Wizard skill. Use it FIRST when the user asks how to do something (how do I, can I, what should I ask) or asks what to do about a problem in NumbersGame, QuickBooks or Xero; not before running a job the user asked for. Each result has a title, section, snippet, url and id; read one in full with get_help_article(id), answer from it, quote its example prompt where it has one, and give the user the url. If nothing matches, say so rather than inventing steps. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › query
What the user wants to do or the problem they describe, in their words, e.g. 'import a bank CSV'.
Clear enough to supply this argument.
params › kind
Only this kind of help: sop (step-by-step procedures), page (help pages), prompt (example prompts), skill (the NumbersGame Wizard skill). Omit to search all.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › limit
How many results, 1-10. Default 6.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_help",
"title": "Search Help",
"description": "Search NumbersGame's own help: the step-by-step SOPs, help pages, example prompts and the NumbersGame Wizard skill. Use it FIRST when the user asks how to do something (how do I, can I, what should I ask) or asks what to do about a problem in NumbersGame, QuickBooks or Xero; not before running a job the user asked for. Each result has a title, section, snippet, url and id; read one in full with get_help_article(id), answer from it, quote its example prompt where it has one, and give the user the url. If nothing matches, say so rather than inventing steps. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"query",
"realm_id"
],
"properties": {
"kind": {
"enum": [
"sop",
"page",
"prompt",
"skill"
],
"type": "string",
"description": "Only this kind of help: sop (step-by-step procedures), page (help pages), prompt (example prompts), skill (the NumbersGame Wizard skill). Omit to search all."
},
"limit": {
"type": "integer",
"maximum": 10,
"minimum": 1,
"description": "How many results, 1-10. Default 6."
},
"query": {
"type": "string",
"maxLength": 200,
"minLength": 2,
"description": "What the user wants to do or the problem they describe, in their words, e.g. 'import a bank CSV'."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Search Help",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Read one NumbersGame help article in full (an SOP step, help page section, example prompt or part of the NumbersGame Wizard skill) by the id search_help returned. The reply is the article, its url, and an outline of the other parts of the same article, so you can read the next step. Answer the user from it, quote its example prompt where it has one, and give them the url. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › id
The id of a search_help result, copied exactly, e.g. 'sop:import-a-bank-csv#step-2-map-the-columns'.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_help_article",
"title": "Get Help Article",
"description": "Read one NumbersGame help article in full (an SOP step, help page section, example prompt or part of the NumbersGame Wizard skill) by the id search_help returned. The reply is the article, its url, and an outline of the other parts of the same article, so you can read the next step. Answer the user from it, quote its example prompt where it has one, and give them the url. NumbersGame data, not ledger data: it never queries QuickBooks or Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "The id of a search_help result, copied exactly, e.g. 'sop:import-a-bank-csv#step-2-map-the-columns'."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Help Article",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Read how the CLIENT'S LEDGER is configured: whether sales tax is switched on, the closing date (QuickBooks) or lock date (Xero) if one is set, the basis reports default to, whether class and department tracking are on, and the home currency. Read-only, one call. Check sales_tax_enabled BEFORE creating a sales receipt, credit memo or refund receipt: on a tax-enabled company a line with no TaxCodeRef is accepted and posts with ZERO tax, and that error lands in a filed return. tax_codes lists the tax codes / tax rates a line (create_invoice: line_items[].tax_code_ref) can name -- for a sales line not one marked purchase_only. QuickBooks: the TaxCode ids; outside the US every sales line needs one. Xero: the organisation's active tax rates, id being the TaxType (e.g. OUTPUT2, INPUT2, NONE) with its rate; Xero calculates the tax. Check closing_date before posting into a prior period. This is NOT get_company_profile, which reads the NumbersGame record and never touches the ledger; this reads the ledger itself. Nothing here can be CHANGED from this connector -- the closing date cannot be set through the API at all -- so report these as facts to work with, and send the user to the ledger's own settings screen to change one. Answers on both QuickBooks and Xero; fields one ledger has no concept of come back null with the reason in `notes`, which is worth reading rather than treating a null as a failure.
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_ledger_settings",
"title": "Get Ledger Settings",
"description": "Read how the CLIENT'S LEDGER is configured: whether sales tax is switched on, the closing date (QuickBooks) or lock date (Xero) if one is set, the basis reports default to, whether class and department tracking are on, and the home currency. Read-only, one call. Check sales_tax_enabled BEFORE creating a sales receipt, credit memo or refund receipt: on a tax-enabled company a line with no TaxCodeRef is accepted and posts with ZERO tax, and that error lands in a filed return. tax_codes lists the tax codes / tax rates a line (create_invoice: line_items[].tax_code_ref) can name -- for a sales line not one marked purchase_only. QuickBooks: the TaxCode ids; outside the US every sales line needs one. Xero: the organisation's active tax rates, id being the TaxType (e.g. OUTPUT2, INPUT2, NONE) with its rate; Xero calculates the tax. Check closing_date before posting into a prior period. This is NOT get_company_profile, which reads the NumbersGame record and never touches the ledger; this reads the ledger itself. Nothing here can be CHANGED from this connector -- the closing date cannot be set through the API at all -- so report these as facts to work with, and send the user to the ledger's own settings screen to change one. Answers on both QuickBooks and Xero; fields one ledger has no concept of come back null with the reason in `notes`, which is worth reading rather than treating a null as a failure.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Get Ledger Settings",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Update this company's Client Profile and/or Open Items (markdown) in NumbersGame. Only the fields you pass are changed. Use after gathering company context or completing a triage. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › client_profile
Markdown: company description — type of company, contacts, financial configuration. Replaces the stored value.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › open_items
Markdown: open bookkeeping items / triage notes. Replaces the stored value.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "set_company_profile",
"title": "Set Company Profile",
"description": "Update this company's Client Profile and/or Open Items (markdown) in NumbersGame. Only the fields you pass are changed. Use after gathering company context or completing a triage. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"open_items": {
"type": "string",
"maxLength": 65536,
"description": "Markdown: open bookkeeping items / triage notes. Replaces the stored value."
},
"client_profile": {
"type": "string",
"maxLength": 65536,
"description": "Markdown: company description — type of company, contacts, financial configuration. Replaces the stored value."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Set Company Profile",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a single one-off task for this company in NumbersGame. It is tracked in the company overview. A task with no due date is posted to the company's Slack channel immediately (once one is assigned); a due-dated one is posted on its due day instead, so future tasks do not notify early. Use for follow-ups you want the bookkeeper to action. This does NOT repeat: for anything recurring (monthly, weekly, quarterly, annual) use create_task_schedule. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › title
Short task title.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › description
Optional details (markdown ok).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › assignee_email
Email of a NumbersGame firm member to assign. Must match an existing member.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › due_date
ISO 8601 due date/time.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › open_item_anchor
Optional anchor linking this task to an Open Items note for this company.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › intent
Required only when the title or description uses recurring wording (monthly, weekly, quarterly, every month, recurring, ...). Such a call is refused until you ask the user what they meant and say so here: 'execute' = do the work now and file nothing, 'one_off' = a single task despite the wording, 'schedule' = a real recurrence (use create_task_schedule instead). Do not set this without asking the user.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_task",
"title": "Create Task",
"description": "Create a single one-off task for this company in NumbersGame. It is tracked in the company overview. A task with no due date is posted to the company's Slack channel immediately (once one is assigned); a due-dated one is posted on its due day instead, so future tasks do not notify early. Use for follow-ups you want the bookkeeper to action. This does NOT repeat: for anything recurring (monthly, weekly, quarterly, annual) use create_task_schedule. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"title",
"realm_id"
],
"properties": {
"title": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Short task title."
},
"intent": {
"enum": [
"execute",
"one_off",
"schedule"
],
"type": "string",
"description": "Required only when the title or description uses recurring wording (monthly, weekly, quarterly, every month, recurring, ...). Such a call is refused until you ask the user what they meant and say so here: 'execute' = do the work now and file nothing, 'one_off' = a single task despite the wording, 'schedule' = a real recurrence (use create_task_schedule instead). Do not set this without asking the user."
},
"due_date": {
"type": "string",
"format": "date-time",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
"description": "ISO 8601 due date/time."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"description": {
"type": "string",
"maxLength": 4000,
"description": "Optional details (markdown ok)."
},
"assignee_email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"description": "Email of a NumbersGame firm member to assign. Must match an existing member."
},
"open_item_anchor": {
"type": "string",
"maxLength": 200,
"description": "Optional anchor linking this task to an Open Items note for this company."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Create Task",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Create a recurring task schedule for this company in NumbersGame: a repeating, recurrence rule that automatically generates a new task every day, week, month, quarter or year. Use this instead of create_task whenever the work repeats (monthly journal entry, weekly reconciliation, quarterly filing, annual close). Requires the company timezone to be set. Confirm the frequency with the user before calling. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › title
Short title for each generated task.
Clear enough to supply this argument.
params › description
Optional details (markdown ok).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › freq
How often the task repeats.
Clear enough to supply this argument.
params › recur_interval
Repeat every N of freq. Default 1. Use 3 with freq=monthly for quarterly.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › anchor_date
Start date, YYYY-MM-DD. Also phases recur_interval > 1 (counted from here).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › byweekday
Weekly only: days of week, 0=Sunday .. 6=Saturday.
Clear enough to supply this argument.
params › bymonthday
Monthly with month_anchor=day_of_month: which day of the month.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › month_anchor
Monthly only: anchor to a fixed day, the first day, or the last day.
Local hour of day the task appears, in the company's timezone. Default 9.
Clear enough to supply this argument.
params › default_assignee_email
Optional email of the NumbersGame firm member to assign every generated task to. Must be a member of this firm. Leave unset to generate unassigned tasks.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_task_schedule",
"title": "Create Recurring Task Schedule",
"description": "Create a recurring task schedule for this company in NumbersGame: a repeating, recurrence rule that automatically generates a new task every day, week, month, quarter or year. Use this instead of create_task whenever the work repeats (monthly journal entry, weekly reconciliation, quarterly filing, annual close). Requires the company timezone to be set. Confirm the frequency with the user before calling. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"title",
"freq",
"anchor_date",
"realm_id"
],
"properties": {
"freq": {
"enum": [
"daily",
"weekly",
"monthly",
"yearly"
],
"type": "string",
"description": "How often the task repeats."
},
"hour": {
"type": "integer",
"maximum": 23,
"minimum": 0,
"description": "Local hour of day the task appears, in the company's timezone. Default 9."
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Short title for each generated task."
},
"bymonth": {
"type": "integer",
"maximum": 12,
"minimum": 1,
"description": "Yearly only: month number, 1=January .. 12=December."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"byweekday": {
"type": "array",
"items": {
"type": "integer",
"maximum": 6,
"minimum": 0
},
"maxItems": 7,
"description": "Weekly only: days of week, 0=Sunday .. 6=Saturday."
},
"bymonthday": {
"type": "integer",
"maximum": 31,
"minimum": 1,
"description": "Monthly with month_anchor=day_of_month: which day of the month."
},
"anchor_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date, YYYY-MM-DD. Also phases recur_interval > 1 (counted from here)."
},
"description": {
"type": "string",
"maxLength": 2000,
"description": "Optional details (markdown ok)."
},
"month_anchor": {
"enum": [
"day_of_month",
"first_day",
"last_day"
],
"type": "string",
"description": "Monthly only: anchor to a fixed day, the first day, or the last day."
},
"recur_interval": {
"type": "integer",
"maximum": 366,
"minimum": 1,
"description": "Repeat every N of freq. Default 1. Use 3 with freq=monthly for quarterly."
},
"default_assignee_email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"description": "Optional email of the NumbersGame firm member to assign every generated task to. Must be a member of this firm. Leave unset to generate unassigned tasks."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Create Recurring Task Schedule",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
List tasks for this company in NumbersGame (newest first), optionally filtered by status. Use to see outstanding work and task ids before updating a status. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › status
Optional: only return tasks in this status.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_tasks",
"title": "List Tasks",
"description": "List tasks for this company in NumbersGame (newest first), optionally filtered by status. Use to see outstanding work and task ids before updating a status. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"status": {
"enum": [
"pending",
"approved",
"completed",
"delayed"
],
"type": "string",
"description": "Optional: only return tasks in this status."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Tasks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Update a task's status in NumbersGame. 'approved' and 'completed' are terminal — once a task is in either, it can't be changed again (the same guard Slack actions use). NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › task_id
Task id (from list_tasks).
Clear enough to supply this argument.
params › status
New status. 'approved' and 'completed' are terminal.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_task_status",
"title": "Update Task Status",
"description": "Update a task's status in NumbersGame. 'approved' and 'completed' are terminal — once a task is in either, it can't be changed again (the same guard Slack actions use). NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"task_id",
"status",
"realm_id"
],
"properties": {
"status": {
"enum": [
"pending",
"approved",
"completed",
"delayed"
],
"type": "string",
"description": "New status. 'approved' and 'completed' are terminal."
},
"task_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Task id (from list_tasks)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Update Task Status",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Publish this company's snapshot (profile, open items, open-task count) into the NumbersGame section of its Slack channel canvas. Only that one delimited section is overwritten; the rest of the canvas is left untouched. No-op if the company has no Slack channel assigned. (Profile/open-item edits also refresh it automatically.) NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "refresh_client_canvas",
"title": "Refresh Client Canvas",
"description": "Publish this company's snapshot (profile, open items, open-task count) into the NumbersGame section of its Slack channel canvas. Only that one delimited section is overwritten; the rest of the canvas is left untouched. No-op if the company has no Slack channel assigned. (Profile/open-item edits also refresh it automatically.) NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Refresh Client Canvas",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Read this company's vendor to account mapping table, also called bank rules (vendor name, account code, account name, confidence high/low, notes, whether the vendor is never billed first or never capitalised, and when each rule was last looked at). ALWAYS call this before classifying or coding transactions, whatever the source - a statement CSV, a bank feed, or a single entry - and pass the descriptors: the firm recorded these rules so they would be applied, and coding a vendor by judgement when a rule already answers it is how a client's books drift from their own stated policy. Pass `descriptors` with the bank strings and the server matches them for you and says how it matched each one: `alias` and `exact` matches on a high-confidence rule can be applied directly, `contains` and `partial` are proposals to put to the user, and anything unmatched is named so you can ask about those and only those. Record what the user confirms so the next statement matches it exactly: descriptors of an EXISTING rule with add_descriptor_aliases, all rules in one call (it changes nothing else on the rule); a vendor with no rule yet with upsert_vendor_mapping, passing the descriptor in `descriptors`. The result says how long ago the set was reviewed: old rules are still the firm's stated coding and should still be applied, but if one contradicts what you are seeing now, say so rather than applying it silently. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › descriptors
Bank statement descriptors to match against this company's rules, exactly as they appear in the file - do not tidy them first, the matcher strips store numbers and reference codes itself. Send the whole statement in ONE call rather than asking per row. You get back, per descriptor, the rules that could describe it, ranked, with the evidence for each; descriptors that match nothing are listed separately and are the only ones a person needs to look at. Omit this to read the whole table as before.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_vendor_mappings",
"title": "Get Vendor Mappings",
"description": "Read this company's vendor to account mapping table, also called bank rules (vendor name, account code, account name, confidence high/low, notes, whether the vendor is never billed first or never capitalised, and when each rule was last looked at). ALWAYS call this before classifying or coding transactions, whatever the source - a statement CSV, a bank feed, or a single entry - and pass the descriptors: the firm recorded these rules so they would be applied, and coding a vendor by judgement when a rule already answers it is how a client's books drift from their own stated policy. Pass `descriptors` with the bank strings and the server matches them for you and says how it matched each one: `alias` and `exact` matches on a high-confidence rule can be applied directly, `contains` and `partial` are proposals to put to the user, and anything unmatched is named so you can ask about those and only those. Record what the user confirms so the next statement matches it exactly: descriptors of an EXISTING rule with add_descriptor_aliases, all rules in one call (it changes nothing else on the rule); a vendor with no rule yet with upsert_vendor_mapping, passing the descriptor in `descriptors`. The result says how long ago the set was reviewed: old rules are still the firm's stated coding and should still be applied, but if one contradicts what you are seeing now, say so rather than applying it silently. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"descriptors": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 500,
"description": "Bank statement descriptors to match against this company's rules, exactly as they appear in the file - do not tidy them first, the matcher strips store numbers and reference codes itself. Send the whole statement in ONE call rather than asking per row. You get back, per descriptor, the rules that could describe it, ranked, with the evidence for each; descriptors that match nothing are listed separately and are the only ones a person needs to look at. Omit this to read the whole table as before."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Vendor Mappings",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Create or update one vendor → account mapping for this company (keyed by vendor name). Populate this from QBO data so future transaction classification can book the vendor's spend to the right account. Set confidence high or low. Whenever a bank descriptor could NOT be matched to a rule and you or the user establishes which vendor it was, call this with `descriptors` so the company learns it - that is what stops the same line being reviewed by hand every month. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › vendor_name
Vendor display name. The mapping is keyed by this within the company; re-using a name updates the existing row.
Clear enough to supply this argument.
params › account_code
Account code the vendor's spend books to (free text, e.g. QBO account number).
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › account_name
Account name (free text).
Explain the meaning of this value, not just its name.
params › confidence
How confident you are in this mapping. Shown green (high) / red (low) / amber (inconsistent — vendor coded to multiple accounts) to the bookkeeper.
Clear enough to supply this argument.
params › notes
Note about the mapping (e.g. caveats, split rules).
Clear enough to supply this argument.
params › transaction_count
How many historical transactions this mapping was derived from (provenance; higher = more reliable).
Clear enough to supply this argument.
params › default_class_id
The class this vendor's spend normally belongs to. Look it up with search_classes. Recorded so bank-feed coding can suggest it instead of leaving every line unclassed - which is what happened before, on every line, for companies that track classes. Ask the user before setting it; it is an assertion about their business, not something to infer from a vendor name.
Clear enough to supply this argument.
params › default_class_name
The class display name, stored alongside the id so a renamed or deleted class reads as a mismatch rather than a bare number.
Clear enough to supply this argument.
params › descriptors
Bank statement descriptors that turned out to be this vendor, VERBATIM as the bank wrote them (e.g. "SQ *BLUE BOTTLE 0472 OAKLAND CA"). Record one whenever you or the user works out who an unmatched descriptor was: get_vendor_mappings then matches that exact string next time instead of guessing from the vendor name, and the transaction stops coming back as manual review every month. Added to whatever is already recorded - nothing you leave out is removed.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "upsert_vendor_mapping",
"title": "Save Vendor Mapping",
"description": "Create or update one vendor → account mapping for this company (keyed by vendor name). Populate this from QBO data so future transaction classification can book the vendor's spend to the right account. Set confidence high or low. Whenever a bank descriptor could NOT be matched to a rule and you or the user establishes which vendor it was, call this with `descriptors` so the company learns it - that is what stops the same line being reviewed by hand every month. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"vendor_name",
"confidence",
"realm_id"
],
"properties": {
"notes": {
"type": "string",
"maxLength": 2000,
"description": "Note about the mapping (e.g. caveats, split rules)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"confidence": {
"enum": [
"high",
"low",
"inconsistent"
],
"type": "string",
"description": "How confident you are in this mapping. Shown green (high) / red (low) / amber (inconsistent — vendor coded to multiple accounts) to the bookkeeper."
},
"descriptors": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 50,
"description": "Bank statement descriptors that turned out to be this vendor, VERBATIM as the bank wrote them (e.g. \"SQ *BLUE BOTTLE 0472 OAKLAND CA\"). Record one whenever you or the user works out who an unmatched descriptor was: get_vendor_mappings then matches that exact string next time instead of guessing from the vendor name, and the transaction stops coming back as manual review every month. Added to whatever is already recorded - nothing you leave out is removed."
},
"vendor_name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Vendor display name. The mapping is keyed by this within the company; re-using a name updates the existing row."
},
"account_code": {
"type": "string",
"maxLength": 100,
"description": "Account code the vendor's spend books to (free text, e.g. QBO account number)."
},
"account_name": {
"type": "string",
"maxLength": 200,
"description": "Account name (free text)."
},
"default_class_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The class this vendor's spend normally belongs to. Look it up with search_classes. Recorded so bank-feed coding can suggest it instead of leaving every line unclassed - which is what happened before, on every line, for companies that track classes. Ask the user before setting it; it is an assertion about their business, not something to infer from a vendor name."
},
"transaction_count": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "How many historical transactions this mapping was derived from (provenance; higher = more reliable)."
},
"default_class_name": {
"type": "string",
"maxLength": 200,
"description": "The class display name, stored alongside the id so a renamed or deleted class reads as a mismatch rather than a bare number."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Save Vendor Mapping",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Headcount and employer payroll cost from Xero UK Payroll, for a Xero company: headcount at each month end with joiners and leavers, and employer cost by month, by department, by employee, plus employer pension and benefits by scheme. Employer cost = earnings + employer pension and benefits + employer National Insurance; Xero's own pay run totalCost leaves employer NI out, so do not quote that as the cost of staff. Posted pay runs only, by payment date; drafts in the range are listed, not counted. Departments come from set_employee_departments, because Xero UK Payroll does not record one: people with none saved are listed under departmentsNotSavedFor and costed under "(no department saved)" - ask the user and save them before presenting a department split. For cost by department as booked in the accounts, compare with qbo_report_profit_and_loss_by_class. Answers only for an organisation running Xero UK Payroll whose connection was approved by a Payroll Administrator; the refusal says which is missing. At most 60 posted pay runs per call: for longer histories ask a year at a time.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
First payment date to include, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › end_date
Last payment date to include, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "report_payroll_costs",
"title": "Payroll Costs and Headcount",
"description": "Headcount and employer payroll cost from Xero UK Payroll, for a Xero company: headcount at each month end with joiners and leavers, and employer cost by month, by department, by employee, plus employer pension and benefits by scheme. Employer cost = earnings + employer pension and benefits + employer National Insurance; Xero's own pay run totalCost leaves employer NI out, so do not quote that as the cost of staff. Posted pay runs only, by payment date; drafts in the range are listed, not counted. Departments come from set_employee_departments, because Xero UK Payroll does not record one: people with none saved are listed under departmentsNotSavedFor and costed under \"(no department saved)\" - ask the user and save them before presenting a department split. For cost by department as booked in the accounts, compare with qbo_report_profit_and_loss_by_class. Answers only for an organisation running Xero UK Payroll whose connection was approved by a Payroll Administrator; the refusal says which is missing. At most 60 posted pay runs per call: for longer histories ask a year at a time.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"start_date",
"end_date",
"realm_id"
],
"properties": {
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last payment date to include, YYYY-MM-DD."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First payment date to include, YYYY-MM-DD."
}
}
}
}
},
"annotations": {
"title": "Payroll Costs and Headcount",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Which vendors a Xero company reports on Form 1099, for a year: Xero's own 1099 report, per vendor the form (1099-NEC, 1099-MISC), the boxes with a non-zero amount, the federal tax classification, and the tax id and its type (SSN, EIN, ITIN, ATIN) the tax id masked to its last 4 digits (NumbersGame never returns a full tax id). Pass contact_id to answer for one vendor. Xero has no 1099 flag on a contact: a vendor is on this report because of the 1099 rules set up in Xero (Reports -> 1099), so a vendor missing here is not set up there or was paid nothing those rules count. US Xero organisations only; Xero produces the report only for an Adviser (or Standard with Reports access), and the refusal says what to check. A vendor's tax number alone is on get_vendor / search_vendors (TaxNumber, TaxNumberType) without this report. On QuickBooks Online the 1099 status is the vendor's Vendor1099 flag, returned by search_vendors and get_vendor; this tool refuses there and says so.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › year
The 1099 tax year, e.g. 2025. Omit for Xero's default year.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › contact_id
A Xero ContactID, to answer for that one vendor.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "report_1099",
"title": "1099 Vendors Report",
"description": "Which vendors a Xero company reports on Form 1099, for a year: Xero's own 1099 report, per vendor the form (1099-NEC, 1099-MISC), the boxes with a non-zero amount, the federal tax classification, and the tax id and its type (SSN, EIN, ITIN, ATIN) the tax id masked to its last 4 digits (NumbersGame never returns a full tax id). Pass contact_id to answer for one vendor. Xero has no 1099 flag on a contact: a vendor is on this report because of the 1099 rules set up in Xero (Reports -> 1099), so a vendor missing here is not set up there or was paid nothing those rules count. US Xero organisations only; Xero produces the report only for an Adviser (or Standard with Reports access), and the refusal says what to check. A vendor's tax number alone is on get_vendor / search_vendors (TaxNumber, TaxNumberType) without this report. On QuickBooks Online the 1099 status is the vendor's Vendor1099 flag, returned by search_vendors and get_vendor; this tool refuses there and says so.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"year": {
"type": "integer",
"maximum": 2100,
"minimum": 2000,
"description": "The 1099 tax year, e.g. 2025. Omit for Xero's default year."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"contact_id": {
"type": "string",
"minLength": 1,
"description": "A Xero ContactID, to answer for that one vendor."
}
}
}
}
},
"annotations": {
"title": "1099 Vendors Report",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Save which department each payroll employee belongs to, for a Xero company. Xero UK Payroll does not record a department, so report_payroll_costs groups employer cost by what is saved here, and search_employees shows it. Saved per company and kept until changed, so ask the user once and save every answer in one call; use the department names the business uses (compare its tracking categories with search_classes if it books by department). Replaces an employee's previous department; null removes it. NumbersGame data: nothing is written to Xero.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Input documentation gives an agent enough context to populate the arguments.
params › assignments › items › employee_id
The employee's Xero payroll employeeID, from search_employees.
Clear enough to supply this argument.
params › assignments › items › department
The department, in the company's own words. null removes the employee's saved department.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "set_employee_departments",
"title": "Save Employee Departments",
"description": "Save which department each payroll employee belongs to, for a Xero company. Xero UK Payroll does not record a department, so report_payroll_costs groups employer cost by what is saved here, and search_employees shows it. Saved per company and kept until changed, so ask the user once and save every answer in one call; use the department names the business uses (compare its tracking categories with search_classes if it books by department). Replaces an employee's previous department; null removes it. NumbersGame data: nothing is written to Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"assignments",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"assignments": {
"type": "array",
"items": {
"type": "object",
"required": [
"employee_id",
"department"
],
"properties": {
"department": {
"anyOf": [
{
"type": "string",
"maxLength": 200,
"minLength": 1
},
{
"type": "null"
}
],
"description": "The department, in the company's own words. null removes the employee's saved department."
},
"employee_id": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The employee's Xero payroll employeeID, from search_employees."
}
},
"additionalProperties": false
},
"maxItems": 500,
"minItems": 1,
"description": "Every assignment in ONE call: all are checked against the payroll first, and nothing is saved if any id is not an employee."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Save Employee Departments",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
List the repeating (recurring) invoice templates in a Xero organisation or a QuickBooks company, sales invoices and bills alike: each one's type (sales_invoice or bill; on QuickBooks also journal_entry, purchase and the other recurring types), contact (the customer, or the supplier on a bill), status, schedule (every N weeks or months, start, next and end date), totals and whether generated invoices are emailed. Xero: deleted templates are left out unless status is DELETED or include_deleted is true, and the schedule carries due date terms. QuickBooks: status is ACTIVE or PAUSED (paused in QuickBooks itself), and each template also has its name and recur_type. get_repeating_invoice returns one template's lines.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › type
Only sales invoice templates or only bill templates. Both ledgers list them together.
Clear enough to supply this argument.
params › status
Only templates with this status. Xero: DRAFT templates generate draft invoices, AUTHORISED ones generate approved invoices. QuickBooks: ACTIVE or PAUSED.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › contact_ref
Only this contact's templates (a customer, or a supplier for bills): the Xero ContactID or the QuickBooks customer or vendor Id.
Clear enough to supply this argument.
params › include_deleted
Xero only: also list deleted templates, which Xero keeps. Default false. QuickBooks keeps no deleted templates.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_repeating_invoices",
"title": "List Repeating Invoices",
"description": "List the repeating (recurring) invoice templates in a Xero organisation or a QuickBooks company, sales invoices and bills alike: each one's type (sales_invoice or bill; on QuickBooks also journal_entry, purchase and the other recurring types), contact (the customer, or the supplier on a bill), status, schedule (every N weeks or months, start, next and end date), totals and whether generated invoices are emailed. Xero: deleted templates are left out unless status is DELETED or include_deleted is true, and the schedule carries due date terms. QuickBooks: status is ACTIVE or PAUSED (paused in QuickBooks itself), and each template also has its name and recur_type. get_repeating_invoice returns one template's lines.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"type": {
"enum": [
"sales_invoice",
"bill"
],
"type": "string",
"description": "Only sales invoice templates or only bill templates. Both ledgers list them together."
},
"status": {
"enum": [
"DRAFT",
"AUTHORISED",
"DELETED",
"ACTIVE",
"PAUSED"
],
"type": "string",
"description": "Only templates with this status. Xero: DRAFT templates generate draft invoices, AUTHORISED ones generate approved invoices. QuickBooks: ACTIVE or PAUSED."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"contact_ref": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "Only this contact's templates (a customer, or a supplier for bills): the Xero ContactID or the QuickBooks customer or vendor Id."
},
"include_deleted": {
"type": "boolean",
"description": "Xero only: also list deleted templates, which Xero keeps. Default false. QuickBooks keeps no deleted templates."
}
}
}
}
},
"annotations": {
"title": "List Repeating Invoices",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Read one repeating (recurring) invoice template: whether it is a sales invoice or a bill, its schedule, contact, lines and totals. Xero adds its history (who created or changed it, and notes); QuickBooks adds its name, recur_type and active flag. list_repeating_invoices returns every template in one call; to read several templates' lines, read them one at a time: many get_repeating_invoice calls in parallel are rate-limited by QuickBooks (code 3001).
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › repeating_invoice_id
The template's id (Xero RepeatingInvoiceID, QuickBooks recurring transaction Id), from list_repeating_invoices.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_repeating_invoice",
"title": "Get Repeating Invoice",
"description": "Read one repeating (recurring) invoice template: whether it is a sales invoice or a bill, its schedule, contact, lines and totals. Xero adds its history (who created or changed it, and notes); QuickBooks adds its name, recur_type and active flag. list_repeating_invoices returns every template in one call; to read several templates' lines, read them one at a time: many get_repeating_invoice calls in parallel are rate-limited by QuickBooks (code 3001).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"repeating_invoice_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"repeating_invoice_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The template's id (Xero RepeatingInvoiceID, QuickBooks recurring transaction Id), from list_repeating_invoices."
}
}
}
}
},
"annotations": {
"title": "Get Repeating Invoice",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Create a repeating sales invoice template, which generates an invoice to the customer on a weekly or monthly schedule from start_date. Sales only. Generated invoices are not emailed by this tool; a person switches emailing on for the template in Xero or QuickBooks. Xero: needs due_date and due_date_type; item ids are resolved to Xero item codes and line amounts are sent tax-exclusive, as create_invoice does; Xero's API refuses a repeating bill. QuickBooks: needs name; the template is QuickBooks' Scheduled type, so QuickBooks creates each invoice on its date and it reaches the books and AR aging then (QuickBooks has no draft invoices); due dates follow the customer's terms. Neither Xero's nor QuickBooks' API can edit or pause an existing template (Xero refuses the change; QuickBooks accepts a pause and ignores it). To pause, resume or change one, do it in Xero or QuickBooks itself, or delete it with delete_repeating_invoice and create the new version with create_repeating_invoice.
The description explains the capability, when to use it, and what to expect.
Inputs70/100
11 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › name
QuickBooks only, and required there: the template's name, unique in the company. Xero templates have no name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › customer_ref
The customer's id: Xero ContactID or QuickBooks customer Id (search_customers).
Clear enough to supply this argument.
params › line_items › items › item_ref
The item's id (QuickBooks), or id or Code (Xero) (search_items).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › line_items › items › qty
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › unit_price
Not provided
Missing description. Explain what this value means and how to supply it.
params › line_items › items › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › every
How many units between invoices: 1 with MONTHLY is every month, 2 with WEEKLY is every two weeks.
Clear enough to supply this argument.
params › unit
Not provided
Missing description. Explain what this value means and how to supply it.
params › start_date
Date of the first invoice, YYYY-MM-DD. On QuickBooks it also sets the day: MONTHLY repeats on its day of the month, WEEKLY on its weekday.
Clear enough to supply this argument.
params › end_date
Date after which no more invoices are generated, YYYY-MM-DD. Omit to repeat until deleted.
Clear enough to supply this argument.
params › due_date
Xero only, and required there: the number used with due_date_type, for example 20 with OFFOLLOWINGMONTH is the 20th of the next month. QuickBooks takes the due date from the customer's terms.
Clear enough to supply this argument.
params › due_date_type
Xero only, and required there. Payment terms: days after the invoice date, days after the end of the invoice month, or a day of the current or following month.
Clear enough to supply this argument.
params › reference
Reference printed on each generated invoice (QuickBooks: the message to the customer).
Clear enough to supply this argument.
params › status
Xero only. DRAFT (default): each generated invoice is a draft a person approves in Xero. AUTHORISED: each one is approved and reaches the books and AR aging on its date. QuickBooks has no draft invoices.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_repeating_invoice",
"title": "Create Repeating Invoice",
"description": "Create a repeating sales invoice template, which generates an invoice to the customer on a weekly or monthly schedule from start_date. Sales only. Generated invoices are not emailed by this tool; a person switches emailing on for the template in Xero or QuickBooks. Xero: needs due_date and due_date_type; item ids are resolved to Xero item codes and line amounts are sent tax-exclusive, as create_invoice does; Xero's API refuses a repeating bill. QuickBooks: needs name; the template is QuickBooks' Scheduled type, so QuickBooks creates each invoice on its date and it reaches the books and AR aging then (QuickBooks has no draft invoices); due dates follow the customer's terms. Neither Xero's nor QuickBooks' API can edit or pause an existing template (Xero refuses the change; QuickBooks accepts a pause and ignores it). To pause, resume or change one, do it in Xero or QuickBooks itself, or delete it with delete_repeating_invoice and create the new version with create_repeating_invoice.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer_ref",
"line_items",
"every",
"unit",
"start_date",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "QuickBooks only, and required there: the template's name, unique in the company. Xero templates have no name."
},
"unit": {
"enum": [
"WEEKLY",
"MONTHLY"
],
"type": "string"
},
"every": {
"type": "integer",
"maximum": 9007199254740991,
"description": "How many units between invoices: 1 with MONTHLY is every month, 2 with WEEKLY is every two weeks.",
"exclusiveMinimum": 0
},
"status": {
"enum": [
"DRAFT",
"AUTHORISED"
],
"type": "string",
"description": "Xero only. DRAFT (default): each generated invoice is a draft a person approves in Xero. AUTHORISED: each one is approved and reaches the books and AR aging on its date. QuickBooks has no draft invoices."
},
"due_date": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Xero only, and required there: the number used with due_date_type, for example 20 with OFFOLLOWINGMONTH is the 20th of the next month. QuickBooks takes the due date from the customer's terms."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Date after which no more invoices are generated, YYYY-MM-DD. Omit to repeat until deleted."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"reference": {
"type": "string",
"description": "Reference printed on each generated invoice (QuickBooks: the message to the customer)."
},
"line_items": {
"type": "array",
"items": {
"type": "object",
"required": [
"item_ref",
"qty",
"unit_price"
],
"properties": {
"qty": {
"type": "number",
"exclusiveMinimum": 0
},
"item_ref": {
"type": "string",
"minLength": 1,
"description": "The item's id (QuickBooks), or id or Code (Xero) (search_items)."
},
"unit_price": {
"type": "number",
"minimum": 0
},
"description": {
"type": "string"
}
},
"additionalProperties": false
},
"minItems": 1
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Date of the first invoice, YYYY-MM-DD. On QuickBooks it also sets the day: MONTHLY repeats on its day of the month, WEEKLY on its weekday."
},
"customer_ref": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The customer's id: Xero ContactID or QuickBooks customer Id (search_customers)."
},
"due_date_type": {
"enum": [
"DAYSAFTERBILLDATE",
"DAYSAFTERBILLMONTH",
"OFCURRENTMONTH",
"OFFOLLOWINGMONTH"
],
"type": "string",
"description": "Xero only, and required there. Payment terms: days after the invoice date, days after the end of the invoice month, or a day of the current or following month."
}
}
}
}
},
"annotations": {
"title": "Create Repeating Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Delete a repeating (recurring) invoice template, so it generates no more invoices. Invoices it already generated are not touched. Neither API can restore a deleted template, so the result returns it in full for recreating with create_repeating_invoice. On Xero, deleting one that is already deleted changes nothing and says so. To stop it only for a while on QuickBooks, pause it in QuickBooks itself instead. Neither Xero's nor QuickBooks' API can edit or pause an existing template (Xero refuses the change; QuickBooks accepts a pause and ignores it). To pause, resume or change one, do it in Xero or QuickBooks itself, or delete it with delete_repeating_invoice and create the new version with create_repeating_invoice.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › repeating_invoice_id
The template's id (Xero RepeatingInvoiceID, QuickBooks recurring transaction Id), from list_repeating_invoices.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_repeating_invoice",
"title": "Delete Repeating Invoice",
"description": "Delete a repeating (recurring) invoice template, so it generates no more invoices. Invoices it already generated are not touched. Neither API can restore a deleted template, so the result returns it in full for recreating with create_repeating_invoice. On Xero, deleting one that is already deleted changes nothing and says so. To stop it only for a while on QuickBooks, pause it in QuickBooks itself instead. Neither Xero's nor QuickBooks' API can edit or pause an existing template (Xero refuses the change; QuickBooks accepts a pause and ignores it). To pause, resume or change one, do it in Xero or QuickBooks itself, or delete it with delete_repeating_invoice and create the new version with create_repeating_invoice.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"repeating_invoice_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"repeating_invoice_id": {
"type": "string",
"pattern": "^(?:\\d{1,20}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
"description": "The template's id (Xero RepeatingInvoiceID, QuickBooks recurring transaction Id), from list_repeating_invoices."
}
}
}
}
},
"annotations": {
"title": "Delete Repeating Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Record bank descriptors the user has confirmed against EXISTING bank rules (vendor mappings), many rules in one call, after propose_descriptor_aliases or get_vendor_mappings proposed them. Only adds: the rule's account, confidence, notes and class are left exactly as they are, which upsert_vendor_mapping would not do unless you restated them. From then on each descriptor matches its rule exactly, on statements and on the bank feed. A descriptor another rule already owns is not added (the result names that rule), because two rules for one descriptor would code it to neither. Where the bank feed's history shows a Plaid merchant id used only by one rule, that id is recorded on the rule too. Only record what the user confirmed: an alias is their statement that the descriptor IS this vendor. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never writes to either.
Describe the returned information so the agent knows whether it will answer the request.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › rules › items › vendor_name
The existing rule's vendor name, as get_vendor_mappings or propose_descriptor_aliases returned it.
Clear enough to supply this argument.
params › rules › items › descriptors
Bank descriptors the user confirmed ARE this vendor, verbatim as the bank wrote them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "add_descriptor_aliases",
"title": "Add Bank Rule Aliases",
"description": "Record bank descriptors the user has confirmed against EXISTING bank rules (vendor mappings), many rules in one call, after propose_descriptor_aliases or get_vendor_mappings proposed them. Only adds: the rule's account, confidence, notes and class are left exactly as they are, which upsert_vendor_mapping would not do unless you restated them. From then on each descriptor matches its rule exactly, on statements and on the bank feed. A descriptor another rule already owns is not added (the result names that rule), because two rules for one descriptor would code it to neither. Where the bank feed's history shows a Plaid merchant id used only by one rule, that id is recorded on the rule too. Only record what the user confirmed: an alias is their statement that the descriptor IS this vendor. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never writes to either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"rules",
"realm_id"
],
"properties": {
"rules": {
"type": "array",
"items": {
"type": "object",
"required": [
"vendor_name",
"descriptors"
],
"properties": {
"descriptors": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Bank descriptors the user confirmed ARE this vendor, verbatim as the bank wrote them."
},
"vendor_name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The existing rule's vendor name, as get_vendor_mappings or propose_descriptor_aliases returned it."
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1,
"description": "Every confirmed rule in ONE call."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Add Bank Rule Aliases",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Start a stored report run for this company in NumbersGame and get a run_id. Call this before running a scheduled review, audit, or book-check prompt so the run shows as 'running' in the company portal, then call complete_report_run with the text result. A report run stores the text output of a Claude task per company (weekly audit, monthly overview, issues report). The type 'dashboard' is special: the latest successful run of that type is rendered as the company's Dashboard page in the portal — to publish a dashboard, read the latest runs of the other types (list_report_runs + get_report_run), compile them into one markdown overview, and store it as a run of type 'dashboard'. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › type
Report type slug for this firm, lowercase snake_case, e.g. 'weekly_audit' or 'monthly_overview'. Auto-created for the firm on first use.
Clear enough to supply this argument.
params › type_label
Optional human-readable name shown in the portal when the type is first created (e.g. 'Weekly Audit').
Clear enough to supply this argument.
params › name
Title for this specific run, e.g. 'Week 29 audit'.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "start_report_run",
"title": "Start Report Run",
"description": "Start a stored report run for this company in NumbersGame and get a run_id. Call this before running a scheduled review, audit, or book-check prompt so the run shows as 'running' in the company portal, then call complete_report_run with the text result. A report run stores the text output of a Claude task per company (weekly audit, monthly overview, issues report). The type 'dashboard' is special: the latest successful run of that type is rendered as the company's Dashboard page in the portal — to publish a dashboard, read the latest runs of the other types (list_report_runs + get_report_run), compile them into one markdown overview, and store it as a run of type 'dashboard'. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"type",
"name",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Title for this specific run, e.g. 'Week 29 audit'."
},
"type": {
"type": "string",
"pattern": "^[a-z0-9_]{1,64}$",
"description": "Report type slug for this firm, lowercase snake_case, e.g. 'weekly_audit' or 'monthly_overview'. Auto-created for the firm on first use."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"type_label": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Optional human-readable name shown in the portal when the type is first created (e.g. 'Weekly Audit')."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Start Report Run",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Complete a stored report run for this company in NumbersGame: set its final status (success, failed, or skipped) and save the Markdown text output. Pair with start_report_run. The bookkeeper reads the saved report in the company portal. Only a run still 'running' can be completed. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs80/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › run_id
Run id returned by start_report_run.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › status
Terminal status: 'success' (attach the report in output), 'failed' (attach a short error), or 'skipped' (nothing to report this period).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › output
The report text as Markdown. Provide on success. Up to ~1 MB.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › error
Short error message when status is 'failed'.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "complete_report_run",
"title": "Complete Report Run",
"description": "Complete a stored report run for this company in NumbersGame: set its final status (success, failed, or skipped) and save the Markdown text output. Pair with start_report_run. The bookkeeper reads the saved report in the company portal. Only a run still 'running' can be completed. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"status",
"realm_id"
],
"properties": {
"error": {
"type": "string",
"maxLength": 4000,
"description": "Short error message when status is 'failed'."
},
"output": {
"type": "string",
"maxLength": 1048576,
"description": "The report text as Markdown. Provide on success. Up to ~1 MB."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Run id returned by start_report_run."
},
"status": {
"enum": [
"success",
"failed",
"skipped"
],
"type": "string",
"description": "Terminal status: 'success' (attach the report in output), 'failed' (attach a short error), or 'skipped' (nothing to report this period)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Complete Report Run",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
List stored report runs for this company in NumbersGame (newest first), optionally filtered by type. Returns each run's id, type, name, status and dates (NOT the full text). Use to see what reports ran and when, and to get a run_id for get_report_run. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › type
Optional: only runs of this type slug (e.g. 'weekly_audit').
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › limit
Max runs to return (default 50, newest first).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_report_runs",
"title": "List Report Runs",
"description": "List stored report runs for this company in NumbersGame (newest first), optionally filtered by type. Returns each run's id, type, name, status and dates (NOT the full text). Use to see what reports ran and when, and to get a run_id for get_report_run. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"type": {
"type": "string",
"pattern": "^[a-z0-9_]{1,64}$",
"description": "Optional: only runs of this type slug (e.g. 'weekly_audit')."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Max runs to return (default 50, newest first)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Report Runs",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Get one stored report run for this company in NumbersGame, including its full Markdown text output. Use to read a previous report's contents — for example to compile a dashboard, summarize across periods, or compare this period to the last. For a run made from a report template it also returns every calculated value, the warnings, the commentary slots and a fresh 24-hour download link. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Input documentation gives an agent enough context to populate the arguments.
params › run_id
Run id (from list_report_runs).
Clear enough to supply this argument.
params › format
For a run made from a report template: which file the fresh download link is for. Default: the template's own format.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_report_run",
"title": "Get Report Run",
"description": "Get one stored report run for this company in NumbersGame, including its full Markdown text output. Use to read a previous report's contents — for example to compile a dashboard, summarize across periods, or compare this period to the last. For a run made from a report template it also returns every calculated value, the warnings, the commentary slots and a fresh 24-hour download link. Accepts a parent company id (pc_...) as realm_id to work on an entity group instead of one company. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"realm_id"
],
"properties": {
"format": {
"enum": [
"xlsx",
"docx",
"pdf",
"md",
"txt"
],
"type": "string",
"description": "For a run made from a report template: which file the fresh download link is for. Default: the template's own format."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Run id (from list_report_runs)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Report Run",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
List the report types defined for this firm in NumbersGame (slug, label, retention days, active). Use to see which report types already exist before starting a run, so you reuse an existing type slug instead of introducing a near-duplicate. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_report_types",
"title": "List Report Types",
"description": "List the report types defined for this firm in NumbersGame (slug, label, retention days, active). Use to see which report types already exist before starting a run, so you reuse an existing type slug instead of introducing a near-duplicate. NumbersGame data, not ledger data: this works the same for a company on QuickBooks Online or on Xero, and never queries either.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Report Types",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
List this firm's approved report templates: each one's name, when to use it, its settings (period span, accounting method, comparison), the calculations it makes and the commentary it asks for. Use it to pick the template for a request like "run the monthly report", or to say what a report contains. Run one with run_report_template. Templates are uploaded and approved in NumbersGame (Prompts & instructions, Reporting). Works the same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_report_templates",
"title": "List Report Templates",
"description": "List this firm's approved report templates: each one's name, when to use it, its settings (period span, accounting method, comparison), the calculations it makes and the commentary it asks for. Use it to pick the template for a request like \"run the monthly report\", or to say what a report contains. Run one with run_report_template. Templates are uploaded and approved in NumbersGame (Prompts & instructions, Reporting). Works the same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Report Templates",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Run one of the firm's report templates for this company and month. The SERVER pulls the ledger, does every calculation and fills the firm's own Excel or Word layout, so the numbers are the same on every run; you never compute or type a figure. Returns the filled report as markdown (report_markdown, commentary slots shown as [[slot:id]]), every value, the commentary slots with the values each may use, warnings for anything left blank and why, and a 24-hour download link. The report is saved under the company in NumbersGame. If it has slots, write them next with write_report_commentary. Values that cannot be produced are blank with a reason, never 0. One template serves QuickBooks Online and Xero companies alike: it names standard groups (Income, Expenses, …), mapped from each ledger's own sections.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › template
The template's name (from list_report_templates) or id.
Clear enough to supply this argument.
params › period
The month the report is for, YYYY-MM ("September 2026" is 2026-09). The template decides the span (month, quarter, year to date, fiscal year) and any comparison.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › format
Which file the download link is for. Default: the template's own format (xlsx or docx). pdf, md and txt are always available too.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "run_report_template",
"title": "Run Report Template",
"description": "Run one of the firm's report templates for this company and month. The SERVER pulls the ledger, does every calculation and fills the firm's own Excel or Word layout, so the numbers are the same on every run; you never compute or type a figure. Returns the filled report as markdown (report_markdown, commentary slots shown as [[slot:id]]), every value, the commentary slots with the values each may use, warnings for anything left blank and why, and a 24-hour download link. The report is saved under the company in NumbersGame. If it has slots, write them next with write_report_commentary. Values that cannot be produced are blank with a reason, never 0. One template serves QuickBooks Online and Xero companies alike: it names standard groups (Income, Expenses, …), mapped from each ledger's own sections.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"template",
"period",
"realm_id"
],
"properties": {
"format": {
"enum": [
"xlsx",
"docx",
"pdf",
"md",
"txt"
],
"type": "string",
"description": "Which file the download link is for. Default: the template's own format (xlsx or docx). pdf, md and txt are always available too."
},
"period": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month the report is for, YYYY-MM (\"September 2026\" is 2026-09). The template decides the span (month, quarter, year to date, fiscal year) and any comparison."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"template": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The template's name (from list_report_templates) or id."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Run Report Template",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Write the commentary into a report made with run_report_template (or by the portal's Run report button or a schedule, which leave slots open when no AI runner wrote them). Only a slot still showing "Commentary N not written" is filled: written text is never overwritten and no number can change. Returns the finished report as markdown and a fresh download link. NumbersGame data only: the same for a QuickBooks Online or a Xero company.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › run_id
The run_id returned by run_report_template (or from list_report_runs).
Clear enough to supply this argument.
params › slot_answers
The commentary per slot, e.g. {"slot_1": "Revenue rose 12% because…"}. Only slots still open are written.
Clear enough to supply this argument.
params › format
Which file the download link is for. Default: the template's own format (xlsx or docx). pdf, md and txt are always available too.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "write_report_commentary",
"title": "Write Report Commentary",
"description": "Write the commentary into a report made with run_report_template (or by the portal's Run report button or a schedule, which leave slots open when no AI runner wrote them). Only a slot still showing \"Commentary N not written\" is filled: written text is never overwritten and no number can change. Returns the finished report as markdown and a fresh download link. NumbersGame data only: the same for a QuickBooks Online or a Xero company.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"slot_answers",
"realm_id"
],
"properties": {
"format": {
"enum": [
"xlsx",
"docx",
"pdf",
"md",
"txt"
],
"type": "string",
"description": "Which file the download link is for. Default: the template's own format (xlsx or docx). pdf, md and txt are always available too."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The run_id returned by run_report_template (or from list_report_runs)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"slot_answers": {
"type": "object",
"description": "The commentary per slot, e.g. {\"slot_1\": \"Revenue rose 12% because…\"}. Only slots still open are written.",
"propertyNames": {
"type": "string",
"pattern": "^slot_\\d+$"
},
"additionalProperties": {
"type": "string",
"maxLength": 4000,
"minLength": 1
}
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Write Report Commentary",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Map a firm account group used by report templates (for example "Marketing" or "Software") to this company's accounts. Each company has its own mapping, because the same line means different accounts at each client. Until a group is mapped, a template value using it is blank with a warning, never 0. Propose the accounts from search_accounts and confirm them with the user before calling. Changes NumbersGame data only, never the ledger. Account ids are QuickBooks numbers or Xero GUIDs, as search_accounts returns them.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › group
The firm group a template names, e.g. "Marketing". Not a standard group such as "Expenses".
Clear enough to supply this argument.
params › account_ids
This company's accounts in the group, by id (search_accounts). Replaces the group's current list for this company.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "set_report_account_group",
"title": "Set Report Account Group",
"description": "Map a firm account group used by report templates (for example \"Marketing\" or \"Software\") to this company's accounts. Each company has its own mapping, because the same line means different accounts at each client. Until a group is mapped, a template value using it is blank with a warning, never 0. Propose the accounts from search_accounts and confirm them with the user before calling. Changes NumbersGame data only, never the ledger. Account ids are QuickBooks numbers or Xero GUIDs, as search_accounts returns them.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"group",
"account_ids",
"realm_id"
],
"properties": {
"group": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "The firm group a template names, e.g. \"Marketing\". Not a standard group such as \"Expenses\"."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_ids": {
"type": "array",
"items": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"maxItems": 500,
"description": "This company's accounts in the group, by id (search_accounts). Replaces the group's current list for this company."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Set Report Account Group",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
The firm's library in NumbersGame (Prompts & instructions): every prompt, instruction and report template with its category, "use when", version, how many companies use it and whether a draft change is waiting; the categories; and the NumbersGame standard prompts offered to the firm. Read this before writing a prompt from scratch: the firm may already have one. can_write says whether this user may change the library. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_library",
"title": "List Library",
"description": "The firm's library in NumbersGame (Prompts & instructions): every prompt, instruction and report template with its category, \"use when\", version, how many companies use it and whether a draft change is waiting; the categories; and the NumbersGame standard prompts offered to the firm. Read this before writing a prompt from scratch: the firm may already have one. can_write says whether this user may change the library. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "List Library",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
One library entry in full: its text, category, "use when", the companies an instruction is attached to, a pending draft, and its version history (who changed it, when, and whether through Claude). For a REPORT TEMPLATE it also returns every version with its check verdict and problems, its calculations, and the LAYOUT AS TEXT: every Excel cell by address (Sheet!B4) or every Word paragraph by number (p12, table cells included). Read the layout before converting a firm's own report with revise_report_template. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › entry
The entry's name or id (list_library lists them).
Clear enough to supply this argument.
params › template_version
Report templates: which version's layout to show. Default: the newest.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_library_entry",
"title": "Get Library Entry",
"description": "One library entry in full: its text, category, \"use when\", the companies an instruction is attached to, a pending draft, and its version history (who changed it, when, and whether through Claude). For a REPORT TEMPLATE it also returns every version with its check verdict and problems, its calculations, and the LAYOUT AS TEXT: every Excel cell by address (Sheet!B4) or every Word paragraph by number (p12, table cells included). Read the layout before converting a firm's own report with revise_report_template. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The entry's name or id (list_library lists them)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"template_version": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Report templates: which version's layout to show. Default: the newest."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Library Entry",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description76/100
The firm's onboarding and initial-checks questions with their answers, and which prompts each answer selects (by question id and answer ids, plus the ledger a prompt fits). The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_onboarding_setup",
"title": "Get Onboarding Setup",
"description": "The firm's onboarding and initial-checks questions with their answers, and which prompts each answer selects (by question id and answer ids, plus the ledger a prompt fits). The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Get Onboarding Setup",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Create a prompt or instruction in the firm's library, or change one. A change is published straight away unless publish is false. Publishing an instruction changes the file of every company it is attached to: the result names them, and their context version is bumped so Claude projects pick up the new text. Every published change is kept, so revert_library_entry can put an earlier version back. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs81/100
7 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › entry
To CHANGE an existing entry: its name or id. Omit to create a new one.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › kind
prompt: copied into a chat and run once. instruction: standing wording printed into the file of each company it is attached to.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › body
The full text (markdown).
Clear enough to supply this argument.
params › category
A category name or id (list_library). A prompt without one goes to Other.
Clear enough to supply this argument.
params › use_when
One line: when to reach for this entry.
Clear enough to supply this argument.
params › publish
Default true: the change is live at once. false: a change to an EXISTING entry is saved as a draft for later (publish_library_draft, or Publish in the portal). A new entry is always live.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "save_library_entry",
"title": "Save Library Entry",
"description": "Create a prompt or instruction in the firm's library, or change one. A change is published straight away unless publish is false. Publishing an instruction changes the file of every company it is attached to: the result names them, and their context version is bumped so Claude projects pick up the new text. Every published change is kept, so revert_library_entry can put an earlier version back. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"kind",
"body",
"realm_id"
],
"properties": {
"body": {
"type": "string",
"maxLength": 32768,
"minLength": 1,
"description": "The full text (markdown)."
},
"kind": {
"enum": [
"prompt",
"instruction"
],
"type": "string",
"description": "prompt: copied into a chat and run once. instruction: standing wording printed into the file of each company it is attached to."
},
"name": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "To CHANGE an existing entry: its name or id. Omit to create a new one."
},
"publish": {
"type": "boolean",
"description": "Default true: the change is live at once. false: a change to an EXISTING entry is saved as a draft for later (publish_library_draft, or Publish in the portal). A new entry is always live."
},
"category": {
"type": "string",
"maxLength": 60,
"description": "A category name or id (list_library). A prompt without one goes to Other."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"use_when": {
"type": "string",
"maxLength": 200,
"description": "One line: when to reach for this entry."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Save Library Entry",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Publish an entry's pending draft so it becomes the live version. Publishing an instruction changes the file of every company it is attached to. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Input documentation gives an agent enough context to populate the arguments.
params › entry
The entry's name or id (list_library lists them).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "publish_library_draft",
"title": "Publish Library Draft",
"description": "Publish an entry's pending draft so it becomes the live version. Publishing an instruction changes the file of every company it is attached to. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The entry's name or id (list_library lists them)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Publish Library Draft",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description82/100
Throw away an entry's pending draft. The live version is unchanged. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Input documentation gives an agent enough context to populate the arguments.
params › entry
The entry's name or id (list_library lists them).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "discard_library_draft",
"title": "Discard Library Draft",
"description": "Throw away an entry's pending draft. The live version is unchanged. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The entry's name or id (list_library lists them)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Discard Library Draft",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Restore an earlier version of a library entry. This is how a mistaken change is undone: the old text comes back as a new version, so nothing in the history is lost. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › entry
The entry's name or id (list_library lists them).
Clear enough to supply this argument.
params › version
The version to restore (get_library_entry lists them). It comes back as a NEW version.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "revert_library_entry",
"title": "Revert Library Entry",
"description": "Restore an earlier version of a library entry. This is how a mistaken change is undone: the old text comes back as a new version, so nothing in the history is lost. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"version",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The entry's name or id (list_library lists them)."
},
"version": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "The version to restore (get_library_entry lists them). It comes back as a NEW version."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Revert Library Entry",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Delete a prompt or instruction from the firm's library. An instruction still attached to companies cannot be deleted: the refusal names them. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › entry
The entry's name or id (list_library lists them).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_library_entry",
"title": "Delete Library Entry",
"description": "Delete a prompt or instruction from the firm's library. An instruction still attached to companies cannot be deleted: the refusal names them. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The entry's name or id (list_library lists them)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Delete Library Entry",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Attach one of the firm's instructions to this company (realm_id), or detach it. The company's file then carries (or no longer carries) the instruction, and its context version is bumped. Only instructions can be attached, never prompts. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › entry
The instruction's name or id.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › attached
Default true (attach). false detaches it.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "attach_instruction",
"title": "Attach Instruction",
"description": "Attach one of the firm's instructions to this company (realm_id), or detach it. The company's file then carries (or no longer carries) the instruction, and its context version is bumped. Only instructions can be attached, never prompts. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"entry",
"realm_id"
],
"properties": {
"entry": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The instruction's name or id."
},
"attached": {
"type": "boolean",
"description": "Default true (attach). false detaches it."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Attach Instruction",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description69/100
Create one of the firm's own library categories. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Explain the meaning of this value, not just its name.
params › name
The new name.
Explain the meaning of this value, not just its name.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_library_category",
"title": "Create Library Category",
"description": "Create one of the firm's own library categories. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "The new name."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Create Library Category",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description73/100
Rename one of the firm's own library categories. Built-in categories (Onboarding, Reporting, …) are fixed. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › category
The category's name or id (list_library).
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › name
The new name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "rename_library_category",
"title": "Rename Library Category",
"description": "Rename one of the firm's own library categories. Built-in categories (Onboarding, Reporting, …) are fixed. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"category",
"name",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "The new name."
},
"category": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "The category's name or id (list_library)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Rename Library Category",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Delete one of the firm's own library categories. Only an empty category can be deleted, and built-in categories (Onboarding, Reporting, …) are fixed. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › category
The category's name or id (list_library).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_library_category",
"title": "Delete Library Category",
"description": "Delete one of the firm's own library categories. Only an empty category can be deleted, and built-in categories (Onboarding, Reporting, …) are fixed. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"category",
"realm_id"
],
"properties": {
"category": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "The category's name or id (list_library)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Delete Library Category",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description69/100
Add a question to the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › flow
Which question set. Default onboarding.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › text
The question text.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "add_onboarding_question",
"title": "Add Onboarding Question",
"description": "Add a question to the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"text",
"realm_id"
],
"properties": {
"flow": {
"enum": [
"onboarding",
"initial_checks"
],
"type": "string",
"description": "Which question set. Default onboarding."
},
"text": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The question text."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Add Onboarding Question",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description72/100
Change the text of one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › id
The question id (get_onboarding_setup).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › text
The question text.
Explain the meaning of this value, not just its name.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "rename_onboarding_question",
"title": "Rename Onboarding Question",
"description": "Change the text of one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"text",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The question id (get_onboarding_setup)."
},
"text": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The question text."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Rename Onboarding Question",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description75/100
Delete one of the firm's onboarding or initial-checks questions, with its answers. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › id
The question id (get_onboarding_setup).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_onboarding_question",
"title": "Delete Onboarding Question",
"description": "Delete one of the firm's onboarding or initial-checks questions, with its answers. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The question id (get_onboarding_setup)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Delete Onboarding Question",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description64/100
Add an answer to one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.
Inputs83/100
Explain the meaning of this value, not just its name.
params › id
The question id (get_onboarding_setup).
Clear enough to supply this argument.
params › text
The answer text.
Explain the meaning of this value, not just its name.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "add_onboarding_answer",
"title": "Add Onboarding Answer",
"description": "Add an answer to one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"text",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The question id (get_onboarding_setup)."
},
"text": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "The answer text."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Add Onboarding Answer",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description71/100
Change the text of an answer to one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs87/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › id
The answer id (get_onboarding_setup).
Clear enough to supply this argument.
params › text
The answer text.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "rename_onboarding_answer",
"title": "Rename Onboarding Answer",
"description": "Change the text of an answer to one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"text",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The answer id (get_onboarding_setup)."
},
"text": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "The answer text."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Rename Onboarding Answer",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description62/100
Delete an answer from one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.
Inputs91/100
Input documentation gives an agent enough context to populate the arguments.
params › id
The answer id (get_onboarding_setup).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "delete_onboarding_answer",
"title": "Delete Onboarding Answer",
"description": "Delete an answer from one of the firm's onboarding or initial-checks questions. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The answer id (get_onboarding_setup)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Delete Onboarding Answer",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Set which onboarding answers select an onboarding prompt, and the ledger it fits. Replaces the prompt's previous selection. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs80/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › prompt
The onboarding prompt's name or id.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › ledger
The ledger the prompt fits. Default any.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › restrictions
Question id → the answer ids the prompt fits. A missing question or [] means any answer.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "set_onboarding_prompt_answers",
"title": "Set Onboarding Prompt Answers",
"description": "Set which onboarding answers select an onboarding prompt, and the ledger it fits. Replaces the prompt's previous selection. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"prompt",
"realm_id"
],
"properties": {
"ledger": {
"enum": [
"any",
"qbo",
"xero"
],
"type": "string",
"description": "The ledger the prompt fits. Default any."
},
"prompt": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The onboarding prompt's name or id."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"restrictions": {
"type": "object",
"description": "Question id → the answer ids the prompt fits. A missing question or [] means any answer.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 100
}
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Set Onboarding Prompt Answers",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description75/100
Take a NumbersGame standard prompt into the firm's library as the firm's own editable copy. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › standard_id
The NumbersGame standard's id (list_library: numbers_game_standards).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "copy_library_standard",
"title": "Copy Library Standard",
"description": "Take a NumbersGame standard prompt into the firm's library as the firm's own editable copy. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"standard_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"standard_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The NumbersGame standard's id (list_library: numbers_game_standards)."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Copy Library Standard",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description79/100
Stop offering a NumbersGame standard prompt to the firm. offer_library_standard brings it back. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › standard_id
The NumbersGame standard's id (list_library: numbers_game_standards).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "hide_library_standard",
"title": "Hide Library Standard",
"description": "Stop offering a NumbersGame standard prompt to the firm. offer_library_standard brings it back. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"standard_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"standard_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The NumbersGame standard's id (list_library: numbers_game_standards)."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Hide Library Standard",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description57/100
Offer a hidden NumbersGame standard prompt to the firm again. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
Describe the concrete operation and its scope instead of restating the tool name.
Inputs92/100
Input documentation gives an agent enough context to populate the arguments.
params › standard_id
The NumbersGame standard's id (list_library: numbers_game_standards).
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "offer_library_standard",
"title": "Offer Library Standard",
"description": "Offer a hidden NumbersGame standard prompt to the firm again. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"standard_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"standard_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The NumbersGame standard's id (list_library: numbers_game_standards)."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Offer Library Standard",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Create a report template in the firm's library, from the firm's OWN Excel or Word report (file_handle, from request_attachment_upload) or from a written brief (a plain layout plus Definitions). The file is checked straight away and the verdict is returned with every problem named by its place. Next: read the layout (get_library_entry), convert it (revise_report_template), preview it (preview_report_template), and approve it (approve_report_template) when the user is satisfied. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
8 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › description
What the report contains, for whoever runs it.
Clear enough to supply this argument.
params › use_when
Not provided
Missing description. Explain what this value means and how to supply it.
params › file_handle
The firm's own Excel/Word report, uploaded with request_attachment_upload. It can be converted next with revise_report_template.
Clear enough to supply this argument.
params › brief › format
Not provided
Missing description. Explain what this value means and how to supply it.
params › brief › sheet_name
Not provided
Missing description. Explain what this value means and how to supply it.
params › brief › rows
Excel: the layout's rows, with markers ({{revenue}}, {{each list}}{{.name}}, {{ask "…"}}).
Clear enough to supply this argument.
params › brief › blocks › items › heading
Not provided
Missing description. Explain what this value means and how to supply it.
params › brief › blocks › items › level
Not provided
Missing description. Explain what this value means and how to supply it.
params › brief › blocks › items › paragraph
Not provided
Missing description. Explain what this value means and how to supply it.
params › brief › blocks › items › table
Not provided
Missing description. Explain what this value means and how to supply it.
params › definitions › settings
e.g. {"period": "month", "compare": "prior_year", "method": "accrual"}
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › definitions › calculations › items › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › definitions › calculations › items › formula
e.g. total(pl, "Income") or lines(pl, "Expenses") | sort(amount, desc)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › definitions › calculations › items › format
money, money_signed, percent, number, integer, text, or list.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_report_template",
"title": "Create Report Template",
"description": "Create a report template in the firm's library, from the firm's OWN Excel or Word report (file_handle, from request_attachment_upload) or from a written brief (a plain layout plus Definitions). The file is checked straight away and the verdict is returned with every problem named by its place. Next: read the layout (get_library_entry), convert it (revise_report_template), preview it (preview_report_template), and approve it (approve_report_template) when the user is satisfied. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"description",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"brief": {
"type": "object",
"required": [
"format"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": [
"string",
"number",
"null"
]
}
},
"maxItems": 500,
"description": "Excel: the layout's rows, with markers ({{revenue}}, {{each list}}{{.name}}, {{ask \"…\"}})."
},
"blocks": {
"type": "array",
"items": {
"type": "object",
"properties": {
"level": {
"type": "integer",
"maximum": 3,
"minimum": 1
},
"table": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": "string"
}
}
},
"heading": {
"type": "string"
},
"paragraph": {
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 500,
"description": "Word: headings, paragraphs and tables, in order. A repeating table row starts {{each list}} and its last cell ends {{end}}."
},
"format": {
"enum": [
"xlsx",
"docx"
],
"type": "string"
},
"sheet_name": {
"type": "string",
"maxLength": 31
}
},
"description": "A plain layout to build the file from, when the firm has no file of its own yet.",
"additionalProperties": false
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"use_when": {
"type": "string",
"maxLength": 200
},
"definitions": {
"type": "object",
"required": [
"calculations"
],
"properties": {
"settings": {
"type": "object",
"description": "e.g. {\"period\": \"month\", \"compare\": \"prior_year\", \"method\": \"accrual\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string"
}
},
"calculations": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"formula"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60
},
"format": {
"type": "string",
"maxLength": 20,
"description": "money, money_signed, percent, number, integer, text, or list."
},
"formula": {
"type": "string",
"maxLength": 500,
"description": "e.g. total(pl, \"Income\") or lines(pl, \"Expenses\") | sort(amount, desc)"
},
"description": {
"type": "string",
"maxLength": 300,
"description": "What the value means, in plain words."
}
},
"additionalProperties": false
},
"maxItems": 200
}
},
"description": "Required with a brief.",
"additionalProperties": false
},
"description": {
"type": "string",
"maxLength": 32768,
"minLength": 1,
"description": "What the report contains, for whoever runs it."
},
"file_handle": {
"type": "string",
"maxLength": 200,
"description": "The firm's own Excel/Word report, uploaded with request_attachment_upload. It can be converted next with revise_report_template."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Create Report Template",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
Convert or change a report template: put markers into named cells or paragraphs, replace typed figures with markers, and write the Definitions. The server edits the firm's own file, so its fonts, colours, column widths and logo stay exactly as they were. The result is a NEW draft version (earlier versions stay), checked at once; the verdict and any problems come back in this result. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
11 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › template
The report template's name or id.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › edits › items › at
Set the text of a cell (Sheet!B4) or paragraph (p12), as get_library_entry lists them.
Clear enough to supply this argument.
params › edits › items › text
With at: the new text, e.g. {{revenue}} or {{each expense_lines}}{{.name}}.
Clear enough to supply this argument.
params › edits › items › find
Replace this phrase wherever it appears in the layout…
Explain the meaning of this value, not just its name.
params › edits › items › replace
…with this, e.g. the typed figure 48,890.00 → {{revenue}}.
Explain the meaning of this value, not just its name.
params › definitions › settings
e.g. {"period": "month", "compare": "prior_year", "method": "accrual"}
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › definitions › calculations › items › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › definitions › calculations › items › formula
e.g. total(pl, "Income") or lines(pl, "Expenses") | sort(amount, desc)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › definitions › calculations › items › format
money, money_signed, percent, number, integer, text, or list.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › file_handle
Instead of edits: a new upload of the whole file (request_attachment_upload), added as the next version as it is.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "revise_report_template",
"title": "Revise Report Template",
"description": "Convert or change a report template: put markers into named cells or paragraphs, replace typed figures with markers, and write the Definitions. The server edits the firm's own file, so its fonts, colours, column widths and logo stay exactly as they were. The result is a NEW draft version (earlier versions stay), checked at once; the verdict and any problems come back in this result. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"template",
"realm_id"
],
"properties": {
"edits": {
"type": "array",
"items": {
"type": "object",
"properties": {
"at": {
"type": "string",
"maxLength": 100,
"description": "Set the text of a cell (Sheet!B4) or paragraph (p12), as get_library_entry lists them."
},
"find": {
"type": "string",
"maxLength": 500,
"description": "Replace this phrase wherever it appears in the layout…"
},
"text": {
"type": "string",
"maxLength": 4000,
"description": "With at: the new text, e.g. {{revenue}} or {{each expense_lines}}{{.name}}."
},
"replace": {
"type": "string",
"maxLength": 4000,
"description": "…with this, e.g. the typed figure 48,890.00 → {{revenue}}."
}
},
"additionalProperties": false
},
"maxItems": 500
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"template": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The report template's name or id."
},
"definitions": {
"type": "object",
"required": [
"calculations"
],
"properties": {
"settings": {
"type": "object",
"description": "e.g. {\"period\": \"month\", \"compare\": \"prior_year\", \"method\": \"accrual\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string"
}
},
"calculations": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"formula"
],
"properties": {
"name": {
"type": "string",
"maxLength": 60
},
"format": {
"type": "string",
"maxLength": 20,
"description": "money, money_signed, percent, number, integer, text, or list."
},
"formula": {
"type": "string",
"maxLength": 500,
"description": "e.g. total(pl, \"Income\") or lines(pl, \"Expenses\") | sort(amount, desc)"
},
"description": {
"type": "string",
"maxLength": 300,
"description": "What the value means, in plain words."
}
},
"additionalProperties": false
},
"maxItems": 200
}
},
"description": "The template's Definitions. Replaces any Definitions already in the file.",
"additionalProperties": false
},
"file_handle": {
"type": "string",
"maxLength": 200,
"description": "Instead of edits: a new upload of the whole file (request_attachment_upload), added as the next version as it is."
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Revise Report Template",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
Approve (publish) a report template version: from now on every run uses it. Only a version that passed its check can be approved. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs58/100
2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › template
Not provided
Missing description. Explain what this value means and how to supply it.
params › version
Default: the newest version that passed its check.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "approve_report_template",
"title": "Approve Report Template",
"description": "Approve (publish) a report template version: from now on every run uses it. Only a version that passed its check can be approved. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"template",
"realm_id"
],
"properties": {
"version": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Default: the newest version that passed its check."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"template": {
"type": "string",
"maxLength": 200,
"minLength": 1
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Approve Report Template",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Fill a template version (draft or approved) for this company (realm_id) and month, and return the report as markdown with its values, warnings and a download link, so it can be checked before approving. Saved under the company as a preview. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs60/100
3 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › template
Not provided
Missing description. Explain what this value means and how to supply it.
params › period
The month to fill it for, YYYY-MM.
Clear enough to supply this argument.
params › version
Default: the newest version (drafts included).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "preview_report_template",
"title": "Preview Report Template",
"description": "Fill a template version (draft or approved) for this company (realm_id) and month, and return the report as markdown with its values, warnings and a download link, so it can be checked before approving. Saved under the company as a preview. Only an owner or admin of the firm may change the library; everyone can read it. The same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"template",
"period",
"realm_id"
],
"properties": {
"period": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month to fill it for, YYYY-MM."
},
"version": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Default: the newest version (drafts included)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"template": {
"type": "string",
"maxLength": 200,
"minLength": 1
}
},
"additionalProperties": false
}
}
},
"annotations": {
"title": "Preview Report Template",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
List the bank connections feeding this QuickBooks company, with their health and booking settings. One connection is one bank login and may contain several accounts. Returns feed_status, so this is the cheapest way to check whether a company has a readable bank feed at all before reporting that it has no bank activity. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_plaid_items",
"title": "List Connected Banks",
"description": "List the bank connections feeding this QuickBooks company, with their health and booking settings. One connection is one bank login and may contain several accounts. Returns feed_status, so this is the cheapest way to check whether a company has a readable bank feed at all before reporting that it has no bank activity. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "List Connected Banks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
List each bank account behind this company's bank connections and the QuickBooks account it maps to. An unmapped account is never booked, so check this before asking why a line was skipped. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A loan account carries `loan`: whether its direction is confirmed (`sign`: nothing on it books until confirmed), who owns it, and the month-end check (`check`: lender's balance against the books'; a difference is shown to the user, never corrected). Each current account also carries the BANK's balance as Plaid last saw it (`balance`, with `as_of`, about daily), free. A balance question is answered from the books first (QuickBooks or Xero); give this one beside it as "per the bank, as of <date>", with the difference, which is what is not yet reconciled (owner, 2026-10-27). `live_refreshes` says how many live balances this company has left this month (10 per company per calendar month, UTC, one per bank login refreshed, reset on the 1st). Only when the person follows up asking for a live, right-now balance, use refresh_live_bank_balance.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_plaid_accounts",
"title": "List Bank Accounts",
"description": "List each bank account behind this company's bank connections and the QuickBooks account it maps to. An unmapped account is never booked, so check this before asking why a line was skipped. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A loan account carries `loan`: whether its direction is confirmed (`sign`: nothing on it books until confirmed), who owns it, and the month-end check (`check`: lender's balance against the books'; a difference is shown to the user, never corrected). Each current account also carries the BANK's balance as Plaid last saw it (`balance`, with `as_of`, about daily), free. A balance question is answered from the books first (QuickBooks or Xero); give this one beside it as \"per the bank, as of <date>\", with the difference, which is what is not yet reconciled (owner, 2026-10-27). `live_refreshes` says how many live balances this company has left this month (10 per company per calendar month, UTC, one per bank login refreshed, reset on the 1st). Only when the person follows up asking for a live, right-now balance, use refresh_live_bank_balance.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "List Bank Accounts",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Fetch a bank login's balance live from the bank, ONLY when the person explicitly asks for a live, current, right-now balance. For any other balance question, give the cached balance list_plaid_accounts returns (free, as of Plaid's last update, about daily). It is TWO calls by design: the first, without confirm_token, uses nothing and returns the cached balance, how many live refreshes this company has left, and a confirm_token; give the person the cached balance, and only if they still want the live one, call again with the same arguments and the token. Each company has 10 live refreshes per calendar month (UTC), the same for every firm; one refresh is one bank login, all of this company's accounts on it; they come back on the 1st. With none left, the first call says so and offers no token. A bank that does not answer (for example one that needs the client to sign in again) gives the refresh back. Works the same for a company on QuickBooks Online or on Xero.
The description explains the capability, when to use it, and what to expect.
Inputs91/100
Input documentation gives an agent enough context to populate the arguments.
params › item_id
The bank login to refresh (item_id from list_plaid_accounts or list_plaid_items). Leave out when the company has one bank login.
Clear enough to supply this argument.
params › account_id
Or an account on that login; the whole login is refreshed, for this company's accounts on it.
Clear enough to supply this argument.
params › confirm_token
Leave out on the first call: you get the cached balance and a confirm_token, and nothing is used. Pass the token only after the person asked for the live balance.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Refresh Live Bank Balance",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "refresh_live_bank_balance",
"title": "Refresh Live Bank Balance",
"description": "Fetch a bank login's balance live from the bank, ONLY when the person explicitly asks for a live, current, right-now balance. For any other balance question, give the cached balance list_plaid_accounts returns (free, as of Plaid's last update, about daily). It is TWO calls by design: the first, without confirm_token, uses nothing and returns the cached balance, how many live refreshes this company has left, and a confirm_token; give the person the cached balance, and only if they still want the live one, call again with the same arguments and the token. Each company has 10 live refreshes per calendar month (UTC), the same for every firm; one refresh is one bank login, all of this company's accounts on it; they come back on the 1st. With none left, the first call says so and offers no token. A bank that does not answer (for example one that needs the client to sign in again) gives the refresh back. Works the same for a company on QuickBooks Online or on Xero.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"item_id": {
"type": "string",
"description": "The bank login to refresh (item_id from list_plaid_accounts or list_plaid_items). Leave out when the company has one bank login."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"description": "Or an account on that login; the whole login is refreshed, for this company's accounts on it."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get the cached balance and a confirm_token, and nothing is used. Pass the token only after the person asked for the live balance."
}
}
}
}
},
"annotations": {
"title": "Refresh Live Bank Balance",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Search this company's bank feed. Use this ONLY for the booking workflow - the user asked to update the bank, reconcile the bank, code the bank feed or catch up the bank. Do NOT use it to answer a question about what is on the account: reading is search_bank_transactions job, whether or not a feed exists, because unbooked feed rows are not the client's books and reading them out invites double counting. If the user wants activity that is not booked yet, offer to update the bank rather than listing feed rows. Requires bank connections set up for the firm. Served from the local cache, so it costs nothing to ask repeatedly. Positive amount = money OUT of the account, uniformly for both bank and credit-card accounts. Returns feed_status: read it before concluding anything from an empty result, because unavailable means no readable feed for this company and history_incomplete means the backfill is still running. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
7 of 9 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › from
Start date, inclusive (YYYY-MM-DD).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
End date, inclusive (YYYY-MM-DD).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › account_id
Restrict to one bank account.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › merchant
Case-insensitive substring of the merchant or bank descriptor.
Clear enough to supply this argument.
params › min_amount
Minimum amount. Positive amounts are money OUT of the account.
Clear enough to supply this argument.
params › max_amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › include_pending
Include pending lines. Off by default: a pending line is replaced by a new posted line when it settles, so including them double-counts.
Clear enough to supply this argument.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_plaid_transactions",
"title": "Search Bank Feed",
"description": "Search this company's bank feed. Use this ONLY for the booking workflow - the user asked to update the bank, reconcile the bank, code the bank feed or catch up the bank. Do NOT use it to answer a question about what is on the account: reading is search_bank_transactions job, whether or not a feed exists, because unbooked feed rows are not the client's books and reading them out invites double counting. If the user wants activity that is not booked yet, offer to update the bank rather than listing feed rows. Requires bank connections set up for the firm. Served from the local cache, so it costs nothing to ask repeatedly. Positive amount = money OUT of the account, uniformly for both bank and credit-card accounts. Returns feed_status: read it before concluding anything from an empty result, because unavailable means no readable feed for this company and history_incomplete means the backfill is still running. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "End date, inclusive (YYYY-MM-DD)."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date, inclusive (YYYY-MM-DD)."
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"merchant": {
"type": "string",
"description": "Case-insensitive substring of the merchant or bank descriptor."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"description": "Restrict to one bank account."
},
"max_amount": {
"type": "number"
},
"min_amount": {
"type": "number",
"description": "Minimum amount. Positive amounts are money OUT of the account."
},
"include_pending": {
"type": "boolean",
"description": "Include pending lines. Off by default: a pending line is replaced by a new posted line when it settles, so including them double-counts."
}
}
}
}
},
"annotations": {
"title": "Search Bank Feed",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Total this company's unbooked bank feed activity by category, merchant or month, to plan a booking run. Requires bank connections set up for the firm. For what the books actually say - spend by vendor, by month, by account - use the QuickBooks side instead: search_bank_transactions and the reports. A feed total is not a books total and the two will not agree while anything is unbooked. Money out and money in are reported separately so a refund never hides inside a spend total. Aggregated in the database, not by reading every row. Returns feed_status: an empty or thin total means nothing until you have read it. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
2 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › group_by
How to group the totals.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › from
Not provided
Missing description. Explain what this value means and how to supply it.
params › to
Not provided
Missing description. Explain what this value means and how to supply it.
params › account_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "plaid_transactions_summary",
"title": "Summarise Bank Spend",
"description": "Total this company's unbooked bank feed activity by category, merchant or month, to plan a booking run. Requires bank connections set up for the firm. For what the books actually say - spend by vendor, by month, by account - use the QuickBooks side instead: search_bank_transactions and the reports. A feed total is not a books total and the two will not agree while anything is unbooked. Money out and money in are reported separately so a refund never hides inside a spend total. Aggregated in the database, not by reading every row. Returns feed_status: an empty or thin total means nothing until you have read it. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"group_by",
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"group_by": {
"enum": [
"category",
"merchant",
"month"
],
"type": "string",
"description": "How to group the totals."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string"
}
}
}
}
},
"annotations": {
"title": "Summarise Bank Spend",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Report each bank connection's last sync, whether its historical backfill has finished, whether it needs re-authentication, how many accounts are still unmapped, and which booking mode and confidence threshold this company runs under. A bank whose history is not yet complete books nothing — check history_complete before reporting that a feed has no activity. Returns feed_status for the company as a whole: unavailable means there is no readable bank feed here at all, which is not the same as a feed with nothing in it. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "plaid_sync_status",
"title": "Bank Feed Status",
"description": "Report each bank connection's last sync, whether its historical backfill has finished, whether it needs re-authentication, how many accounts are still unmapped, and which booking mode and confidence threshold this company runs under. A bank whose history is not yet complete books nothing — check history_complete before reporting that a feed has no activity. Returns feed_status for the company as a whole: unavailable means there is no readable bank feed here at all, which is not the same as a feed with nothing in it. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Bank Feed Status",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Start here when the user asks to update the bank, reconcile the bank, code the bank feed or catch up the bank. For each unbooked bank transaction, return the suggested QuickBooks treatment with a confidence score computed server-side, any structural vetoes holding it for review, and whether it would post under this company's current booking mode. A veto is not a dead end: most can be cleared by the user reviewing the line and confirming it, so report what is held and why, in plain language, rather than stopping. Writes nothing to the ledger. It stores the proposals as a booking run (a new one, or the open run_id given) that the user sees in the portal, and adds run_id, state, review_token and a version per line: show the user the lines that need their yes, then post with post_booking_run. Loan and mortgage accounts (QuickBooks): nothing on a loan books until its direction is confirmed (loan_sign_unconfirmed; list_plaid_accounts shows each loan's state), and then every loan booking needs the user's approval, one line at a time with their own reason (loan_booking_needs_approval): a payment paired with a bank or card line is one Transfer into the loan (the bank line and the loan line are the same booking: approve one), a draw paired with a deposit is a Transfer out of the loan and is flagged as a draw for the user to check, and interest or a late fee is a JournalEntry to the loan's interest or service-charges account. A loan line no rule covers (loan_line_unclassified) is booked by approving it as a JournalEntry naming the account the user says (interest, fee, escrow). A payment with no line on a connected bank waits for it (loan_payment_unpaired). A loan marked personal is not booked in this company (loan_personal_not_booked: mark it ignored); its payment from the business account books to the owner's account. On Xero, loan lines and a bank line paired with one are not booked yet (account_type_not_booked). Works on Xero as well as QuickBooks. The already-in-the-ledger check reconstructs the Xero account's movements and RECONCILES them against Xero's own bank summary; a period that cannot be proved complete is reported as a failed lookup and held, never as a clear ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is. Also returns possible_duplicates_after_booking: an entry we did not create, on the same register, for the same amount within 3 days of a line we booked in the last 45 days -- usually the ledger's own bank feed adding that line again (Add instead of Match). Tell the user to check the pair and delete the extra one; it is a warning, never a hold. Registers that could not be read are listed in possible_duplicates_check_skipped.
The description explains the capability, when to use it, and what to expect.
Inputs55/100
3 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › from
Only consider transactions on or after this date.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › run_id
Add these proposals to this open run instead of starting a new one.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "propose_bank_coding",
"title": "Propose Bank Coding",
"description": "Start here when the user asks to update the bank, reconcile the bank, code the bank feed or catch up the bank. For each unbooked bank transaction, return the suggested QuickBooks treatment with a confidence score computed server-side, any structural vetoes holding it for review, and whether it would post under this company's current booking mode. A veto is not a dead end: most can be cleared by the user reviewing the line and confirming it, so report what is held and why, in plain language, rather than stopping. Writes nothing to the ledger. It stores the proposals as a booking run (a new one, or the open run_id given) that the user sees in the portal, and adds run_id, state, review_token and a version per line: show the user the lines that need their yes, then post with post_booking_run. Loan and mortgage accounts (QuickBooks): nothing on a loan books until its direction is confirmed (loan_sign_unconfirmed; list_plaid_accounts shows each loan's state), and then every loan booking needs the user's approval, one line at a time with their own reason (loan_booking_needs_approval): a payment paired with a bank or card line is one Transfer into the loan (the bank line and the loan line are the same booking: approve one), a draw paired with a deposit is a Transfer out of the loan and is flagged as a draw for the user to check, and interest or a late fee is a JournalEntry to the loan's interest or service-charges account. A loan line no rule covers (loan_line_unclassified) is booked by approving it as a JournalEntry naming the account the user says (interest, fee, escrow). A payment with no line on a connected bank waits for it (loan_payment_unpaired). A loan marked personal is not booked in this company (loan_personal_not_booked: mark it ignored); its payment from the business account books to the owner's account. On Xero, loan lines and a bank line paired with one are not booked yet (account_type_not_booked). Works on Xero as well as QuickBooks. The already-in-the-ledger check reconstructs the Xero account's movements and RECONCILES them against Xero's own bank summary; a period that cannot be proved complete is reported as a failed lookup and held, never as a clear ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is. Also returns possible_duplicates_after_booking: an entry we did not create, on the same register, for the same amount within 3 days of a line we booked in the last 45 days -- usually the ledger's own bank feed adding that line again (Add instead of Match). Tell the user to check the pair and delete the extra one; it is a warning, never a hold. Registers that could not be read are listed in possible_duplicates_check_skipped.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only consider transactions on or after this date."
},
"limit": {
"type": "integer",
"maximum": 300,
"minimum": 1
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Add these proposals to this open run instead of starting a new one."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Propose Bank Coding",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Read-only. For a company on accrual basis, list the bank-rule vendors that have no bill or bill payment anywhere in QuickBooks, as CANDIDATES for the never-billed flag. Marking a vendor never-billed lets its payments post as a direct expense instead of waiting for a bill to match. Writes nothing and sets no flag: a human must confirm each one, and the tool reports how much billing history it could actually see so thin evidence is visible rather than hidden. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "propose_never_billed_vendors",
"title": "Propose Never-Billed Vendors",
"description": "Read-only. For a company on accrual basis, list the bank-rule vendors that have no bill or bill payment anywhere in QuickBooks, as CANDIDATES for the never-billed flag. Marking a vendor never-billed lets its payments post as a direct expense instead of waiting for a bill to match. Writes nothing and sets no flag: a human must confirm each one, and the tool reports how much billing history it could actually see so thin evidence is visible rather than hidden. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Propose Never-Billed Vendors",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Read-only. For a company with a bank feed, list the bank descriptors the feed could NOT code although one of the company's own bank rules plainly describes them (e.g. "INSTAMED REGENCE BL" next to the rule "Regence BL"), grouped by rule, with the words that agreed, how many transactions and how much money each covers, and any other rule that could also be meant. Rules match exactly by design, so these lines sit in review until somebody says the descriptor IS that vendor. Writes nothing: put the list to the user, and record the ones they confirm with add_descriptor_aliases in ONE call; from then on the feed codes them exactly. Also reports how many rules could be given Plaid's stable merchant id from the feed's own history, which add_descriptor_aliases records. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records and the company's rules, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "propose_descriptor_aliases",
"title": "Propose Bank Rule Aliases",
"description": "Read-only. For a company with a bank feed, list the bank descriptors the feed could NOT code although one of the company's own bank rules plainly describes them (e.g. \"INSTAMED REGENCE BL\" next to the rule \"Regence BL\"), grouped by rule, with the words that agreed, how many transactions and how much money each covers, and any other rule that could also be meant. Rules match exactly by design, so these lines sit in review until somebody says the descriptor IS that vendor. Writes nothing: put the list to the user, and record the ones they confirm with add_descriptor_aliases in ONE call; from then on the feed codes them exactly. Also reports how many rules could be given Plaid's stable merchant id from the feed's own history, which add_descriptor_aliases records. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records and the company's rules, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Propose Bank Rule Aliases",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
Align the title with the capability actually described by this tool.
Description93/100
Post one bank transaction into QuickBooks. The confidence score and any vetoes are recomputed server-side and the company's booking mode decides whether it posts - a line held for review is reported, not forced. When a line is held only because its score is under the threshold, the result says so and nothing is structurally wrong with it: show the user what you propose, and if they confirm it, post it through the bank booking run rather than stopping: propose_bank_coding opens the run (get_booking_run { latest: true } resumes one), then post_booking_run posts what the user said yes to. Idempotent: a transaction already booked, or the other leg of a transfer already booked, is never posted twice. Works on Xero as well as QuickBooks: an expense books as a BankTransaction SPEND, money in as a RECEIVE, a transfer as a BankTransfer and a bill settlement as a Payment. Xero requires a contact on a bank transaction where QuickBooks treats the payee as optional, so a line with no vendor is refused by name rather than posted without one.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
7 of 13 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › transaction_id
The Plaid transaction to book.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › qbo_object_type
The QuickBooks object to create. Use 'ignored' to record a decision not to book this line.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › qbo_account_id
Category account for the expense or income side.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › vendor_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › class_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › matched_doc_id
Open bill this payment settles, for a BillPayment.
Missing description. Explain what this value means and how to supply it.
params › splits › anyOf › 0 › items › class_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › splits › anyOf › 0 › items › amount
Not provided
Missing description. Explain what this value means and how to supply it.
params › splits › anyOf › 0 › items › tax_code_id
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › tax_code_id
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "book_bank_transaction",
"title": "Book Bank Transaction",
"description": "Post one bank transaction into QuickBooks. The confidence score and any vetoes are recomputed server-side and the company's booking mode decides whether it posts - a line held for review is reported, not forced. When a line is held only because its score is under the threshold, the result says so and nothing is structurally wrong with it: show the user what you propose, and if they confirm it, post it through the bank booking run rather than stopping: propose_bank_coding opens the run (get_booking_run { latest: true } resumes one), then post_booking_run posts what the user said yes to. Idempotent: a transaction already booked, or the other leg of a transfer already booked, is never posted twice. Works on Xero as well as QuickBooks: an expense books as a BankTransaction SPEND, money in as a RECEIVE, a transfer as a BankTransfer and a bill settlement as a Payment. Xero requires a contact on a bank transaction where QuickBooks treats the payee as optional, so a line with no vendor is refused by name rather than posted without one.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transaction_id",
"qbo_object_type",
"realm_id"
],
"properties": {
"memo": {
"type": [
"string",
"null"
]
},
"splits": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"qbo_account_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"exclusiveMinimum": 0
},
"class_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"qbo_account_id": {
"type": "string",
"minLength": 1
}
}
}
},
{
"type": "null"
}
],
"description": "Multiple category lines on one bank line, e.g. payroll into wages and taxes."
},
"class_id": {
"type": [
"string",
"null"
]
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"vendor_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"matched_doc_id": {
"type": [
"string",
"null"
],
"description": "Open bill this payment settles, for a BillPayment."
},
"qbo_account_id": {
"type": [
"string",
"null"
],
"description": "Category account for the expense or income side."
},
"transaction_id": {
"type": "string",
"description": "The Plaid transaction to book."
},
"qbo_object_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"BillPayment",
"ignored"
],
"type": "string",
"description": "The QuickBooks object to create. Use 'ignored' to record a decision not to book this line."
}
}
}
}
},
"annotations": {
"title": "Book Bank Transaction",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Book many bank transactions in one call. Each line goes through the same scoring, vetoes and claim-first ordering as a single booking, so a batch can never post something a single call would refuse. Returns a per-line result; one failure does not abort the rest. If lines come back held only on score, that is not a dead end: summarise them for the user, and on their confirmation post those through the bank booking run: propose_bank_coding opens the run (get_booking_run { latest: true } resumes one), then post_booking_run posts what the user said yes to. Follow with report_bank_booking_run. Works on Xero as well as QuickBooks, mapping each line to a BankTransaction, BankTransfer or Payment as its treatment implies.
The description explains the capability, when to use it, and what to expect.
Inputs23/100
3 of 13 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › decisions › items › transaction_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › qbo_object_type
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › qbo_account_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › vendor_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › class_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › matched_doc_id
Not provided
Missing description. Explain what this value means and how to supply it.
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › decisions › items › memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › tax_code_id
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "bulk_book_bank_transactions",
"title": "Book Bank Transactions (Batch)",
"description": "Book many bank transactions in one call. Each line goes through the same scoring, vetoes and claim-first ordering as a single booking, so a batch can never post something a single call would refuse. Returns a per-line result; one failure does not abort the rest. If lines come back held only on score, that is not a dead end: summarise them for the user, and on their confirmation post those through the bank booking run: propose_bank_coding opens the run (get_booking_run { latest: true } resumes one), then post_booking_run posts what the user said yes to. Follow with report_bank_booking_run. Works on Xero as well as QuickBooks, mapping each line to a BankTransaction, BankTransfer or Payment as its treatment implies.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"decisions",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"decisions": {
"type": "array",
"items": {
"type": "object",
"required": [
"transaction_id",
"qbo_object_type"
],
"properties": {
"memo": {
"type": [
"string",
"null"
]
},
"splits": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"qbo_account_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"exclusiveMinimum": 0
},
"class_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"qbo_account_id": {
"type": "string",
"minLength": 1
}
}
}
},
{
"type": "null"
}
]
},
"class_id": {
"type": [
"string",
"null"
]
},
"vendor_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"matched_doc_id": {
"type": [
"string",
"null"
]
},
"qbo_account_id": {
"type": [
"string",
"null"
]
},
"transaction_id": {
"type": "string"
},
"qbo_object_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"BillPayment",
"ignored"
],
"type": "string"
}
}
},
"maxItems": 100,
"minItems": 1,
"description": "One entry per bank transaction to book."
}
}
}
}
},
"annotations": {
"title": "Book Bank Transactions (Batch)",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
Align the title with the capability actually described by this tool.
Description89/100
Replaced by the bank booking run: this tool posts nothing. It records the decisions it is sent into the company's open booking run and answers replaced_by_run with run_id, a review_token and the recorded lines; show the user those lines, then post with post_booking_run { run_id, review_token }. To approve bank lines, use propose_bank_coding, show the user the lines that need their yes, then post_booking_run. Works on Xero as well as QuickBooks.
The description explains the capability, when to use it, and what to expect.
Inputs33/100
5 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › decisions › items › transaction_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › qbo_object_type
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › qbo_account_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › vendor_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › class_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › matched_doc_id
Not provided
Missing description. Explain what this value means and how to supply it.
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › decisions › items › memo
Not provided
Missing description. Explain what this value means and how to supply it.
params › decisions › items › tax_code_id
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › decisions › items › reason
Why THIS line is right, in the user's words. Required for a line held as already in the general ledger (why it is not a duplicate), as a capital purchase (why it is expensed or capitalised as chosen), or as a loan booking - the batch reason does not clear those. Optional otherwise.
Clear enough to supply this argument.
params › reason
What the user checked and why these are right, covering the batch. Optional - leave it out when the user simply confirmed a list they had read. Stored on every booking. Write what the person actually told you, not a restatement of the tool's purpose.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Approve And Book Reviewed Bank Transactions",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "approve_bank_transactions",
"title": "Approve And Book Reviewed Bank Transactions",
"description": "Replaced by the bank booking run: this tool posts nothing. It records the decisions it is sent into the company's open booking run and answers replaced_by_run with run_id, a review_token and the recorded lines; show the user those lines, then post with post_booking_run { run_id, review_token }. To approve bank lines, use propose_bank_coding, show the user the lines that need their yes, then post_booking_run. Works on Xero as well as QuickBooks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"decisions",
"realm_id"
],
"properties": {
"reason": {
"anyOf": [
{
"type": "string",
"maxLength": 500
},
{
"type": "null"
}
],
"description": "What the user checked and why these are right, covering the batch. Optional - leave it out when the user simply confirmed a list they had read. Stored on every booking. Write what the person actually told you, not a restatement of the tool's purpose."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"decisions": {
"type": "array",
"items": {
"type": "object",
"required": [
"transaction_id",
"qbo_object_type"
],
"properties": {
"memo": {
"type": [
"string",
"null"
]
},
"reason": {
"anyOf": [
{
"type": "string",
"maxLength": 500
},
{
"type": "null"
}
],
"description": "Why THIS line is right, in the user's words. Required for a line held as already in the general ledger (why it is not a duplicate), as a capital purchase (why it is expensed or capitalised as chosen), or as a loan booking - the batch reason does not clear those. Optional otherwise."
},
"splits": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"qbo_account_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"exclusiveMinimum": 0
},
"class_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"qbo_account_id": {
"type": "string",
"minLength": 1
}
}
}
},
{
"type": "null"
}
]
},
"class_id": {
"type": [
"string",
"null"
]
},
"vendor_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"matched_doc_id": {
"type": [
"string",
"null"
]
},
"qbo_account_id": {
"type": [
"string",
"null"
]
},
"transaction_id": {
"type": "string"
},
"qbo_object_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"BillPayment",
"JournalEntry",
"ignored"
],
"type": "string"
}
}
},
"maxItems": 100,
"minItems": 1,
"description": "One entry per reviewed bank transaction. Ids must be named explicitly - there is no approve-all."
}
}
}
}
},
"annotations": {
"title": "Approve And Book Reviewed Bank Transactions",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
List bank transactions that were coded and then held for review, with the coding that was chosen, the score, the vetoes and the plain-language reason for each. Call this at the START of a bank-feed session: a hold made in an earlier conversation is stored, so the categorisation does not have to be redone. Every line is re-scored as it is read, so what you see is today's answer, not the one recorded when it was held. Read the clearance field on each line: none means it only missed the confidence bar; sweepable means a person can approve it and it may go in a batch; confirm means a person can approve it but it must be shown on its own and carry their reason; correct means resend the coding fixed; ignore_only means payroll, which is cleared with mark_plaid_transaction_ignored and never posted from the feed; settable_in_chat means a company setting nobody has stated, which set_accounting_policy can fix; needs_setting means the portal; blocked means QuickBooks could not be read or there is nothing to post, so retry rather than override. Show the user the reasons, not the veto names. Read-only. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › limit
How many held lines to return. Default 100, newest hold first.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "List Bank Transactions Held For Review",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_held_bank_transactions",
"title": "List Bank Transactions Held For Review",
"description": "List bank transactions that were coded and then held for review, with the coding that was chosen, the score, the vetoes and the plain-language reason for each. Call this at the START of a bank-feed session: a hold made in an earlier conversation is stored, so the categorisation does not have to be redone. Every line is re-scored as it is read, so what you see is today's answer, not the one recorded when it was held. Read the clearance field on each line: none means it only missed the confidence bar; sweepable means a person can approve it and it may go in a batch; confirm means a person can approve it but it must be shown on its own and carry their reason; correct means resend the coding fixed; ignore_only means payroll, which is cleared with mark_plaid_transaction_ignored and never posted from the feed; settable_in_chat means a company setting nobody has stated, which set_accounting_policy can fix; needs_setting means the portal; blocked means QuickBooks could not be read or there is nothing to post, so retry rather than override. Show the user the reasons, not the veto names. Read-only. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger. A FEED IS ONE SOURCE OF ROWS, NOT A PREREQUISITE FOR BANK WORK: when this company has no readable feed, ask for the transactions as a CSV, a statement, or rows pasted into the chat and do the same job -- vendor rules from get_vendor_mappings, what is already posted from search_bank_transactions, and the posting itself through bulk_create_transactions (dry_run first, statement totals required). Never report bank work as unavailable because a feed is.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "How many held lines to return. Default 100, newest hold first."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "List Bank Transactions Held For Review",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Report what was posted to QuickBooks from the bank feed, what was reversed, what failed or is unconfirmed, and how many lines remain unbooked. Because confident lines post without prior approval, this report plus one-click reversal is the control surface — run it after every booking session. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › since
ISO 8601 timestamp, e.g. 2026-07-01T00:00:00Z. Omit for everything recorded for this company.
Clear enough to supply this argument.
params › run_id
Report this run only, every line in exactly one bucket per bank account.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "report_bank_booking_run",
"title": "Bank Booking Report",
"description": "Report what was posted to QuickBooks from the bank feed, what was reversed, what failed or is unconfirmed, and how many lines remain unbooked. Because confident lines post without prior approval, this report plus one-click reversal is the control surface — run it after every booking session. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"since": {
"type": "string",
"format": "date-time",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
"description": "ISO 8601 timestamp, e.g. 2026-07-01T00:00:00Z. Omit for everything recorded for this company."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Report this run only, every line in exactly one bucket per bank account."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Bank Booking Report",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Read a bank booking run (propose_bank_coding starts one): every line with its current coding, version, vetoes and reasons, re-scored now; the per-account counts (posted, ignored, unconfirmed, in flight, failed, left for the user, blocked, to post); the run's state; and a review_token covering the lines returned. Use { latest: true } to resume in a new conversation: a yes from an earlier conversation does not carry over, so show the user the lines that need their yes and ask again before post_booking_run. state: show = some lines changed or were not shown with this token (show them, ask again); busy = another call is posting; confirming = settle unconfirmed lines with reverse_bank_booking resolve_unconfirmed (other lines may still post); open = ask for the yes, then post; done = report the counts. Writes nothing to the ledger. Works on Xero as well as QuickBooks.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
4 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › run_id
The run to read. Give this or latest.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › latest
true: the newest open run for this company (resume in a new conversation).
Clear enough to supply this argument.
params › review_token
The token from the previous result in this conversation, so the new token keeps covering what it covered.
Clear enough to supply this argument.
params › cursor
Not provided
Missing description. Explain what this value means and how to supply it.
params › limit
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_booking_run",
"title": "Get Bank Booking Run",
"description": "Read a bank booking run (propose_bank_coding starts one): every line with its current coding, version, vetoes and reasons, re-scored now; the per-account counts (posted, ignored, unconfirmed, in flight, failed, left for the user, blocked, to post); the run's state; and a review_token covering the lines returned. Use { latest: true } to resume in a new conversation: a yes from an earlier conversation does not carry over, so show the user the lines that need their yes and ask again before post_booking_run. state: show = some lines changed or were not shown with this token (show them, ask again); busy = another call is posting; confirming = settle unconfirmed lines with reverse_bank_booking resolve_unconfirmed (other lines may still post); open = ask for the yes, then post; done = report the counts. Writes nothing to the ledger. Works on Xero as well as QuickBooks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 300,
"minimum": 1
},
"cursor": {
"type": "string"
},
"latest": {
"type": "boolean",
"description": "true: the newest open run for this company (resume in a new conversation)."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The run to read. Give this or latest."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"review_token": {
"type": "string",
"description": "The token from the previous result in this conversation, so the new token keeps covering what it covered."
}
}
}
}
},
"annotations": {
"title": "Get Bank Booking Run",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Change lines in a bank booking run before posting: re-code a line (treatment, the same shape as a booking decision), leave it for the user with a reason, or put it back to the suggested coding. A new coding is scored like any proposal; a coding that is wrong comes back with clearance correct, not as a refusal. The result is the changed lines in full plus a new review_token covering them: show the user these lines, then post with post_booking_run and that token. Writes nothing to the ledger. Works on Xero as well as QuickBooks.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
6 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › run_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › review_token
The token from the previous result, so the new one keeps covering it.
Clear enough to supply this argument.
params › changes › items › transaction_id
Not provided
Missing description. Explain what this value means and how to supply it.
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › changes › items › treatment › memo
Not provided
Missing description. Explain what this value means and how to supply it.
The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate.
Clear enough to supply this argument.
params › changes › items › left_for_user
Leave this line for the user, with the reason.
Clear enough to supply this argument.
params › changes › items › back_to_suggested
Undo a change: back to the server's suggested coding.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_booking_run",
"title": "Update Bank Booking Run",
"description": "Change lines in a bank booking run before posting: re-code a line (treatment, the same shape as a booking decision), leave it for the user with a reason, or put it back to the suggested coding. A new coding is scored like any proposal; a coding that is wrong comes back with clearance correct, not as a refusal. The result is the changed lines in full plus a new review_token covering them: show the user these lines, then post with post_booking_run and that token. Writes nothing to the ledger. Works on Xero as well as QuickBooks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"run_id",
"changes",
"realm_id"
],
"properties": {
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"changes": {
"type": "array",
"items": {
"type": "object",
"required": [
"transaction_id"
],
"properties": {
"treatment": {
"type": "object",
"required": [
"qbo_object_type"
],
"properties": {
"memo": {
"type": [
"string",
"null"
]
},
"splits": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"qbo_account_id",
"amount"
],
"properties": {
"amount": {
"type": "number",
"exclusiveMinimum": 0
},
"class_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"qbo_account_id": {
"type": "string",
"minLength": 1
}
}
}
},
{
"type": "null"
}
]
},
"class_id": {
"type": [
"string",
"null"
]
},
"vendor_id": {
"type": [
"string",
"null"
]
},
"tax_code_id": {
"type": [
"string",
"null"
],
"description": "The sales tax code the bookkeeper states for this line, from get_ledger_settings tax_codes: a QuickBooks tax code id (e.g. GST/HST in Canada), or a Xero TaxType (e.g. INPUT2 on a spend, OUTPUT2 on a receipt). The bank amount is treated as tax-INCLUSIVE: the tax is recorded inside it, so the total still equals the bank line. Never guess one; omit it to book without a stated rate (on Xero the account's default rate applies, inside the bank amount). On a QuickBooks split, every line needs a code or none does; on Xero a split line without one takes its account's default rate."
},
"matched_doc_id": {
"type": [
"string",
"null"
]
},
"qbo_account_id": {
"type": [
"string",
"null"
]
},
"qbo_object_type": {
"enum": [
"Purchase",
"Deposit",
"Transfer",
"BillPayment",
"JournalEntry",
"ignored"
],
"type": "string"
}
},
"description": "The user's coding for this line, replacing the suggestion."
},
"left_for_user": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Leave this line for the user, with the reason."
},
"transaction_id": {
"type": "string"
},
"back_to_suggested": {
"type": "boolean",
"const": true,
"description": "Undo a change: back to the server's suggested coding."
}
}
},
"maxItems": 100,
"minItems": 1
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"review_token": {
"type": "string",
"description": "The token from the previous result, so the new one keeps covering it."
}
}
}
}
},
"annotations": {
"title": "Update Bank Booking Run",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Post the lines of a bank booking run that the user said yes to: { run_id, review_token } from the last result that showed them. Posts the STORED coding of each line, so never re-type it; changes go through update_booking_run first. Every line goes through the same re-score, vetoes, booking mode and claim-first booking as before, and one line's refusal never stops the others. Per line: proposal_stale means the line changed after it was shown (the result carries the new version and a token covering it: show it, then post again); review_required means a line held on a veto only a person's yes lifts was not covered by your token (call get_booking_run with this run_id, show the line, then post with that token); a line held only on its score posts and is marked not_reviewed; a line whose coding lacks what its type needs (an account, a transfer's other register, a bill payment's bill or vendor, a Xero contact) is held before anything is written, with what is missing named: re-code it with update_booking_run. Lines held as already in the general ledger, a capital purchase or a loan booking need the user's own sentence in line_reasons. A connection set to propose only posts nothing. Follow with report_bank_booking_run { run_id }. Works on Xero as well as QuickBooks, mapping each line to its Xero equivalent.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
5 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › run_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › review_token
The token from the last result that showed these lines.
Clear enough to supply this argument.
params › transaction_ids
Omit to post every line to post that the token covers.
Clear enough to supply this argument.
params › reason
What the user checked, for the batch. Optional when they confirmed a list they had read.
Clear enough to supply this argument.
params › line_reasons
{ transaction_id: reason } in the user's words. Required for a line held as already in the general ledger, a capital purchase, or a loan booking; the batch reason does not clear those.
Clear enough to supply this argument.
params › displayed › items › transaction_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › displayed › items › proposal_hash
Not provided
Missing description. Explain what this value means and how to supply it.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "post_booking_run",
"title": "Post Bank Booking Run",
"description": "Post the lines of a bank booking run that the user said yes to: { run_id, review_token } from the last result that showed them. Posts the STORED coding of each line, so never re-type it; changes go through update_booking_run first. Every line goes through the same re-score, vetoes, booking mode and claim-first booking as before, and one line's refusal never stops the others. Per line: proposal_stale means the line changed after it was shown (the result carries the new version and a token covering it: show it, then post again); review_required means a line held on a veto only a person's yes lifts was not covered by your token (call get_booking_run with this run_id, show the line, then post with that token); a line held only on its score posts and is marked not_reviewed; a line whose coding lacks what its type needs (an account, a transfer's other register, a bill payment's bill or vendor, a Xero contact) is held before anything is written, with what is missing named: re-code it with update_booking_run. Lines held as already in the general ledger, a capital purchase or a loan booking need the user's own sentence in line_reasons. A connection set to propose only posts nothing. Follow with report_bank_booking_run { run_id }. Works on Xero as well as QuickBooks, mapping each line to its Xero equivalent.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"reason": {
"type": "string",
"maxLength": 500,
"description": "What the user checked, for the batch. Optional when they confirmed a list they had read."
},
"run_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"displayed": {
"type": "array",
"items": {
"type": "object",
"required": [
"transaction_id",
"proposal_hash"
],
"properties": {
"proposal_hash": {
"type": "string"
},
"transaction_id": {
"type": "string"
}
}
},
"maxItems": 100,
"description": "NumbersGame portal only; refused from any other client."
},
"line_reasons": {
"type": "object",
"description": "{ transaction_id: reason } in the user's words. Required for a line held as already in the general ledger, a capital purchase, or a loan booking; the batch reason does not clear those.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string",
"maxLength": 500
}
},
"review_token": {
"type": "string",
"description": "The token from the last result that showed these lines."
},
"transaction_ids": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 100,
"minItems": 1,
"description": "Omit to post every line to post that the token covers."
}
}
}
}
},
"annotations": {
"title": "Post Bank Booking Run",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Delete the QuickBooks object created for a bank transaction and return the line to the review queue. Idempotent. A line claimed by an entry made by hand (create_purchase, create_deposit, create_transfer, create_bill_payment, create_journal_entry and the connectors' bookings record the feed line they match as booked by that entry) is RELEASED instead: the line returns to the queue and that entry is not deleted. A booking that was claimed but never confirmed (the ledger may or may not have it) is not deleted on a guess: look in the ledger, then call again with resolve_unconfirmed "posted" (and ledger_object_id) or "not_posted". Works on Xero as well as QuickBooks.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › transaction_id
The Plaid transaction whose booking should be unwound.
Clear enough to supply this argument.
params › resolve_unconfirmed
Only for a booking that was claimed but never confirmed. After looking in the ledger: "not_posted" returns the line to the review queue; "posted" records the object you found (give ledger_object_id) as this line's booking. Nothing is deleted either way.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › ledger_object_id
With resolve_unconfirmed "posted": the id of the object in the ledger for THIS bank line. A later reversal deletes this object, so copy it exactly.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Reverse a Bank Booking",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "reverse_bank_booking",
"title": "Reverse a Bank Booking",
"description": "Delete the QuickBooks object created for a bank transaction and return the line to the review queue. Idempotent. A line claimed by an entry made by hand (create_purchase, create_deposit, create_transfer, create_bill_payment, create_journal_entry and the connectors' bookings record the feed line they match as booked by that entry) is RELEASED instead: the line returns to the queue and that entry is not deleted. A booking that was claimed but never confirmed (the ledger may or may not have it) is not deleted on a guess: look in the ledger, then call again with resolve_unconfirmed \"posted\" (and ledger_object_id) or \"not_posted\". Works on Xero as well as QuickBooks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transaction_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"transaction_id": {
"type": "string",
"description": "The Plaid transaction whose booking should be unwound."
},
"ledger_object_id": {
"type": "string",
"minLength": 1,
"description": "With resolve_unconfirmed \"posted\": the id of the object in the ledger for THIS bank line. A later reversal deletes this object, so copy it exactly."
},
"resolve_unconfirmed": {
"enum": [
"posted",
"not_posted"
],
"type": "string",
"description": "Only for a booking that was claimed but never confirmed. After looking in the ledger: \"not_posted\" returns the line to the review queue; \"posted\" records the object you found (give ledger_object_id) as this line's booking. Nothing is deleted either way."
}
}
}
}
},
"annotations": {
"title": "Reverse a Bank Booking",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Record a decision not to book a bank transaction, so it stops appearing in the review queue. Reversible with reverse_bank_booking, which returns it to the queue. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs67/100
2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › transaction_id
Not provided
Missing description. Explain what this value means and how to supply it.
params › reason
Why this line is not being booked — recorded for the audit trail.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Ignore a Bank Transaction",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "mark_plaid_transaction_ignored",
"title": "Ignore a Bank Transaction",
"description": "Record a decision not to book a bank transaction, so it stops appearing in the review queue. Reversible with reverse_bank_booking, which returns it to the queue. Works the same for a company on QuickBooks Online or on Xero: this reads the bank feed's own records, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"transaction_id",
"reason",
"realm_id"
],
"properties": {
"reason": {
"type": "string",
"minLength": 1,
"description": "Why this line is not being booked — recorded for the audit trail."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"transaction_id": {
"type": "string"
}
}
}
}
},
"annotations": {
"title": "Ignore a Bank Transaction",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
Shorten the title to an action and subject; move usage details into the description.
Description93/100
Set how this company's books are kept: cash or accrual basis, the capitalization threshold above which a purchase is held for a person to decide, whether an applicable financial statement applies, and whether every accrual payment must settle an open bill. Use it when a bank line or a statement line is held because nobody has stated the accounting basis, or when the user asks to change one of these. Ask the user for the value and use their answer - never choose a basis yourself to clear a hold, because that changes how every line in the company is coded. Every field is optional and anything omitted is left as it is. Owner, admin and member can all set this; the same settings also live on the company page in the portal. These are properties of the books, used by statement imports as well as bank connections. Works the same for a company on QuickBooks Online or on Xero: this writes NumbersGame's own settings, not the ledger.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › basis
Cash or accrual, as stated by the user. ASK - never infer this from the books, from the vendor list, or from what would clear a hold. Omit to leave it unchanged.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › capitalization_threshold
The amount at or above which a purchase is held for a human to decide whether it is a fixed asset. Omit to leave unchanged. Null clears it, which falls back to the statutory safe harbour - 2500, or 5000 where an applicable financial statement is asserted.
Clear enough to supply this argument.
params › has_applicable_financial_statement
TRUE when this client has an applicable financial statement - broadly, an audited one. It raises the de minimis safe harbour from 2500 to 5000. Assert this only when the user says so.
Clear enough to supply this argument.
params › unbilled_ceiling
Only used when strict bill matching is on: the amount below which a vendor with no bank rule may post a direct expense on accrual. Cannot exceed the capitalization threshold. Null means no backstop.
Clear enough to supply this argument.
params › strict_bill_matching
TRUE = every accrual money-out line must settle an open bill, and one that matches none is held. FALSE, the default, holds a line only when the vendor has an open bill that did not fit this payment. Turn it on only if the user asks for it.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "set_accounting_policy",
"title": "Set This Company's Accounting Policy",
"description": "Set how this company's books are kept: cash or accrual basis, the capitalization threshold above which a purchase is held for a person to decide, whether an applicable financial statement applies, and whether every accrual payment must settle an open bill. Use it when a bank line or a statement line is held because nobody has stated the accounting basis, or when the user asks to change one of these. Ask the user for the value and use their answer - never choose a basis yourself to clear a hold, because that changes how every line in the company is coded. Every field is optional and anything omitted is left as it is. Owner, admin and member can all set this; the same settings also live on the company page in the portal. These are properties of the books, used by statement imports as well as bank connections. Works the same for a company on QuickBooks Online or on Xero: this writes NumbersGame's own settings, not the ledger.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"basis": {
"anyOf": [
{
"enum": [
"cash",
"accrual"
],
"type": "string"
},
{
"type": "null"
}
],
"description": "Cash or accrual, as stated by the user. ASK - never infer this from the books, from the vendor list, or from what would clear a hold. Omit to leave it unchanged."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"unbilled_ceiling": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "Only used when strict bill matching is on: the amount below which a vendor with no bank rule may post a direct expense on accrual. Cannot exceed the capitalization threshold. Null means no backstop."
},
"strict_bill_matching": {
"type": [
"boolean",
"null"
],
"description": "TRUE = every accrual money-out line must settle an open bill, and one that matches none is held. FALSE, the default, holds a line only when the vendor has an open bill that did not fit this payment. Turn it on only if the user asks for it."
},
"capitalization_threshold": {
"anyOf": [
{
"type": "number",
"minimum": 0
},
{
"type": "null"
}
],
"description": "The amount at or above which a purchase is held for a human to decide whether it is a fixed asset. Omit to leave unchanged. Null clears it, which falls back to the statutory safe harbour - 2500, or 5000 where an applicable financial statement is asserted."
},
"has_applicable_financial_statement": {
"type": [
"boolean",
"null"
],
"description": "TRUE when this client has an applicable financial statement - broadly, an audited one. It raises the de minimis safe harbour from 2500 to 5000. Assert this only when the user says so."
}
}
}
}
},
"annotations": {
"title": "Set This Company's Accounting Policy",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
List the Stripe accounts connected to this company: account id, live or test mode, whether the connection works or was disconnected (uninstalled in Stripe, or access lapsed), when its token last refreshed, and how far setup has got -- which summary accounts are mapped, which payout destinations are mapped, the summary cadence (daily or monthly), time zone and AR cutoff date, and how the business uses Stripe (business_model: merchant, platform or connected_account; platform comes with a warning to pass on before booking, its revenue_policy (agent or principal; null = not chosen yet, so it cannot book), its unsettled_warning_days (after how many days a separate-charge job not yet paid out in full is warned about), its marketplace_tag (the metadata marking a marketplace payment; anything without it books as the platform's own sale; null = not set, nothing told apart), its recognition_timing (stripe_evidence, or completion_date: on accrual the fee or sale is recognised in the period of the job's completion date, metadata completion_date_key), and its accounting_basis and accounting_basis_note to pass on). Reads no Stripe data (on Xero it reads the mapped Stripe Clearing account, which must be a current asset). Call this first; every other stripe_ tool needs a connected, set-up account. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_status",
"title": "Stripe Connection Status",
"description": "List the Stripe accounts connected to this company: account id, live or test mode, whether the connection works or was disconnected (uninstalled in Stripe, or access lapsed), when its token last refreshed, and how far setup has got -- which summary accounts are mapped, which payout destinations are mapped, the summary cadence (daily or monthly), time zone and AR cutoff date, and how the business uses Stripe (business_model: merchant, platform or connected_account; platform comes with a warning to pass on before booking, its revenue_policy (agent or principal; null = not chosen yet, so it cannot book), its unsettled_warning_days (after how many days a separate-charge job not yet paid out in full is warned about), its marketplace_tag (the metadata marking a marketplace payment; anything without it books as the platform's own sale; null = not set, nothing told apart), its recognition_timing (stripe_evidence, or completion_date: on accrual the fee or sale is recognised in the period of the job's completion date, metadata completion_date_key), and its accounting_basis and accounting_basis_note to pass on). Reads no Stripe data (on Xero it reads the mapped Stripe Clearing account, which must be a current asset). Call this first; every other stripe_ tool needs a connected, set-up account. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
}
}
}
}
},
"annotations": {
"title": "Stripe Connection Status",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Map the ledger accounts a Stripe connection posts to, map each Stripe payout destination to a ledger bank account, and set the summary cadence, time zone and AR cutoff. On a marketplace platform the reply also gives the company's Accounting basis (accounting_basis: cash, accrual, or null when not set on the company page) and accounting_basis_note, which says what NumbersGame books on that basis and, on accrual, the month-end adjustment the bookkeeper books from stripe_provider_payable_report: pass it on. BEFORE creating anything, look for existing accounts with search_accounts and pass them in `accounts`; create only what is missing (a taken name returns the existing account; an existing account of the wrong type is reported, not mapped). Confirm with the bookkeeper before creating accounts. Settings merge with what is already saved. Returns what is still unmapped. Stripe Receivables and Stripe Clearing belong to ONE Stripe account: with a second Stripe account on the company, give it its own (e.g. "Stripe Clearing (acct …1234)"); a warning names any other connection mapped to the same one. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs51/100
22 of 40 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › accounts › receivables
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › clearing
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › revenue
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › tax_collected
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › fees
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › bad_debt
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › chargebacks
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › customer_credits
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › legacy_receivables
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › provider_payable
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › platform_fee_revenue
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › platform_fee_refunds
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › due_from_providers
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › stripe_reserve
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › provider_costs
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › platform_discounts
Not provided
Missing description. Explain what this value means and how to supply it.
params › accounts › customer_cash_balance
Not provided
Missing description. Explain what this value means and how to supply it.
params › create › items › key
Not provided
Missing description. Explain what this value means and how to supply it.
params › create › items › name
Defaults: Stripe Receivables, Stripe Clearing, Stripe Sales, Stripe Tax Collected, Stripe Fees, Bad Debt, Stripe Chargebacks, Stripe Customer Credits, Stripe Receivables - opening (legacy_receivables: the Stripe invoices open at the start date, for stripe_opening_balances); platform slots: Provider Payable, Platform Fee Revenue, Platform Fee Refunds, Due from Providers, Stripe Reserve, Provider Costs.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › create › items › acct_num
Account code. REQUIRED on Xero.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payout_banks
Stripe payout destination (ba_... from stripe_list_payouts) -> the ledger bank account it pays into.
Clear enough to supply this argument.
params › cadence
One summary journal per day or per calendar month. Default monthly. Can be changed later, but time already booked is never booked again: a period overlapping a booked one answers already_booked.
Clear enough to supply this argument.
params › timezone
IANA time zone the periods are cut in, e.g. America/New_York. Default UTC. As with cadence, a change cannot re-book time already booked.
Clear enough to supply this argument.
params › cutoff_date
Invoices finalized before this date are legacy: they stay out of Stripe Receivables.
Clear enough to supply this argument.
params › deferred_revenue_account
Deferred revenue account id (an Other Current Liability). On the ng_summary path it turns on the month-end deferral of multi-month revenue (stripe_propose_deferral_journal); on stripe_revrec, Stripe's DeferredRevenue accounts book to it.
Clear enough to supply this argument.
params › revrec_accounts
Stripe Revenue Recognition account names the Rev Rec journal could not resolve (stripe_propose_revrec_journal lists them) -> ledger account id.
Clear enough to supply this argument.
params › revenue_path
Which journal carries Stripe revenue, AR and cash into the ledger: ng_summary (the NumbersGame period summary, default) or stripe_revrec (Stripe Revenue Recognition's journal, booked from Stripe; the NG summary is then refused so nothing posts twice). Decide it with the person at onboarding (stripe_onboarding_assess recommends one).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › business_model
How the business uses Stripe, as the person answered the first onboarding checkpoint question: merchant (sells its own products or services), platform (collects payments for others and pays them out through Stripe, a marketplace; then ask how it is booked and save revenue_policy: agent (recommended): the full payment is held in Provider Payable and only the platform's fee is revenue; or principal: the full sale is revenue and the provider's share a cost (Provider Costs), booked once Stripe shows the provider's share; it needs the platform accounts for its policy and books on the ng_summary path only), or connected_account (gets paid through someone else's platform). Save what the person said, not what the data suggests. Usually it is already chosen on the company page's Stripe card (Standard = merchant, Marketplace / intermediary = platform); stripe_status shows it.
Clear enough to supply this argument.
params › refund_fee_policy
Platform only. When a destination charge that pays the provider a set amount (transfer_data[amount]) is refunded, or a separate charge (separate charges and transfers) is refunded after its fee was released: pro_rata (default) gives back the platform's fee share, in proportion to the refund, through Platform Fee Refunds; platform_keeps books the whole refund against Provider Payable. Application-fee refunds follow Stripe and do not use it. Ask the person; do not guess.
Clear enough to supply this argument.
params › revenue_policy
Platform only, REQUIRED there (no default): how the platform's payments are booked; until it is set, a platform's periods are needs_setup. agent (recommended): the full payment is held in Provider Payable and only the platform's fee is revenue. principal: the full sale is revenue and the provider's share is a cost (Provider Costs; provider_payable and provider_costs are then required): every payment is held in Provider Payable and transfers reduce it, as under agent; on the same Stripe evidence that releases an agent's fee (an application fee line, a transfer amount set on the payment, or a separate charge's transfers reaching the expected share) the sale is recognised: Cr revenue (the whole sale without tax), Dr Provider Costs (the provider's share), and the fee from Provider Payable (or, on an application fee line, from Stripe Clearing). After recognition a refund takes the provider's part off revenue and Provider Costs, never more than was recognised (a fee the platform keeps stays in revenue); a dispute or failed payment takes the provider's share off them, its fee share going to Chargebacks as under agent, and after the provider was paid puts the provider's share on Due from Providers, with a warning. Principal covers destination charges and separate charges and transfers: an application fee from a direct charge is held for review under principal. It is the accountant's decision (who controls the service: the platform or the provider); ask the person, do not guess. Changing it after periods were booked is allowed and warned: the booked periods stay as they were, and a sale already recognised keeps its treatment for its later refunds, disputes and fee refunds.
Clear enough to supply this argument.
params › job_link
Platform only, for separate charges and transfers: how a transfer finds its charge (its job). transfer_group (default: the transfer and the charge share a transfer_group) or source_transaction (the transfer was created with source_transaction = the charge). Any other value is read as a metadata key, which is not built: every such job is held. Ask the person how their platform links transfers to charges; do not guess.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › expected_share_key
Platform only, for separate charges and transfers: the charge metadata key holding the provider's expected share in integer minor units (cents). Default provider_amount; use the platform's own name for it (e.g. provider_share). For a payment of a Stripe invoice the key is read from the invoice when the charge lacks it (Stripe does not copy invoice metadata to the payment). The platform's fee (charge amount - expected share) is released once the job's transfers reach it; a charge without an integer there is held, and the proposal names it.
Clear enough to supply this argument.
params › provider_account_key
Platform only, for separate charges and transfers, no default: the metadata key (on the charge, or on the Stripe invoice it pays) naming the provider's connected account (acct_...), e.g. provider_account. When set, a transfer of a job to a different connected account gets a WARNING in the proposal (the provider may have been paid wrongly); nothing is held. Ask the person which key their platform writes; do not guess.
Clear enough to supply this argument.
params › marketplace_tag › anyOf › 0 › key
The metadata key, e.g. charge_type.
Clear enough to supply this argument.
params › marketplace_tag › anyOf › 0 › value
The value that marks a marketplace payment, e.g. marketplace. Compared exactly.
Clear enough to supply this argument.
params › unsettled_warning_days
Platform only, for separate charges and transfers: after how many days a job whose transfers have not reached the provider's expected share gets a WARNING, in the period proposal and in stripe_tie_out P2. Default 30. A warning only: nothing is held for it.
Clear enough to supply this argument.
params › recognition_timing
Platform only: when the platform's fee (agent) or the sale (principal) is recognised. stripe_evidence (default): when Stripe shows it (an application fee, a transfer amount set on the payment, or the provider's share fully paid). completion_date: on an ACCRUAL company, in the period of the job's completion date read from metadata (completion_date_key) on the Stripe invoice the payment paid, else its PaymentIntent, else the charge; a job without a date stays in Provider Payable and is listed; ignored on cash. Set it only when the platform writes that date into Stripe; ask, do not guess. Changing it after periods were booked applies from the first period not yet booked.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › completion_date_key
Platform, recognition_timing completion_date: the metadata key holding the job's completion date (YYYY-MM-DD in the company's time zone, a timestamp with Z or an offset, or unix seconds). Default job_completed_at; event platforms often use event_date.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_setup_accounts",
"title": "Set Up Stripe Accounts",
"description": "Map the ledger accounts a Stripe connection posts to, map each Stripe payout destination to a ledger bank account, and set the summary cadence, time zone and AR cutoff. On a marketplace platform the reply also gives the company's Accounting basis (accounting_basis: cash, accrual, or null when not set on the company page) and accounting_basis_note, which says what NumbersGame books on that basis and, on accrual, the month-end adjustment the bookkeeper books from stripe_provider_payable_report: pass it on. BEFORE creating anything, look for existing accounts with search_accounts and pass them in `accounts`; create only what is missing (a taken name returns the existing account; an existing account of the wrong type is reported, not mapped). Confirm with the bookkeeper before creating accounts. Settings merge with what is already saved. Returns what is still unmapped. Stripe Receivables and Stripe Clearing belong to ONE Stripe account: with a second Stripe account on the company, give it its own (e.g. \"Stripe Clearing (acct …1234)\"); a warning names any other connection mapped to the same one. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"create": {
"type": "array",
"items": {
"type": "object",
"required": [
"key"
],
"properties": {
"key": {
"enum": [
"receivables",
"clearing",
"revenue",
"tax_collected",
"fees",
"bad_debt",
"chargebacks",
"customer_credits",
"legacy_receivables",
"provider_payable",
"platform_fee_revenue",
"platform_fee_refunds",
"due_from_providers",
"stripe_reserve",
"provider_costs",
"platform_discounts",
"customer_cash_balance"
],
"type": "string"
},
"name": {
"type": "string",
"maxLength": 100,
"description": "Defaults: Stripe Receivables, Stripe Clearing, Stripe Sales, Stripe Tax Collected, Stripe Fees, Bad Debt, Stripe Chargebacks, Stripe Customer Credits, Stripe Receivables - opening (legacy_receivables: the Stripe invoices open at the start date, for stripe_opening_balances); platform slots: Provider Payable, Platform Fee Revenue, Platform Fee Refunds, Due from Providers, Stripe Reserve, Provider Costs."
},
"acct_num": {
"type": "string",
"maxLength": 20,
"description": "Account code. REQUIRED on Xero."
}
}
},
"description": "Accounts to create because the chart has none. A name that already exists is reused, not duplicated -- but look first with search_accounts, since a matching account may have another name."
},
"cadence": {
"enum": [
"daily",
"monthly"
],
"type": "string",
"description": "One summary journal per day or per calendar month. Default monthly. Can be changed later, but time already booked is never booked again: a period overlapping a booked one answers already_booked."
},
"accounts": {
"type": "object",
"properties": {
"fees": {
"type": "string",
"minLength": 1
},
"revenue": {
"type": "string",
"minLength": 1
},
"bad_debt": {
"type": "string",
"minLength": 1
},
"clearing": {
"type": "string",
"minLength": 1
},
"chargebacks": {
"type": "string",
"minLength": 1
},
"receivables": {
"type": "string",
"minLength": 1
},
"tax_collected": {
"type": "string",
"minLength": 1
},
"provider_costs": {
"type": "string",
"minLength": 1
},
"stripe_reserve": {
"type": "string",
"minLength": 1
},
"customer_credits": {
"type": "string",
"minLength": 1
},
"provider_payable": {
"type": "string",
"minLength": 1
},
"due_from_providers": {
"type": "string",
"minLength": 1
},
"legacy_receivables": {
"type": "string",
"minLength": 1
},
"platform_discounts": {
"type": "string",
"minLength": 1
},
"platform_fee_refunds": {
"type": "string",
"minLength": 1
},
"platform_fee_revenue": {
"type": "string",
"minLength": 1
},
"customer_cash_balance": {
"type": "string",
"minLength": 1
}
},
"description": "Existing ledger accounts to use, by key -> ledger account id. Keys: receivables (Stripe Receivables, an Other Current Asset -- NOT the ledger's A/R), clearing (Stripe Clearing, an account of its own: on QuickBooks an Other Current Asset (created as one; an existing Bank-type account is accepted too), on Xero a current asset account (Xero type CURRENT, never a Bank account, since a Xero manual journal cannot post to one); never a real bank account and never one with a bank feed -- a NumbersGame bank feed is refused, but a bank connected inside QuickBooks or Xero itself cannot be seen, so check that too), revenue, tax_collected (a liability for Stripe-calculated tax), fees, bad_debt (an expense, or an allowance account if the firm writes off against one), chargebacks, customer_credits (a liability), legacy_receivables (optional: the account that carries receivables from before the cutoff). Only for a marketplace platform (business_model platform), more are required, because its summary posts to them. Booked as agent (revenue_policy agent), five: provider_payable (an Other Current Liability: money collected for providers, not yet paid out), platform_fee_revenue and platform_fee_refunds (Income), due_from_providers and stripe_reserve (Other Current Asset). Booked as principal (revenue_policy principal), four: provider_payable (as for agent: every payment is held there until its sale is recognised), provider_costs (Cost of Goods Sold: the provider's share of each recognised sale), due_from_providers and stripe_reserve; the sale itself goes to revenue. Optional, agent only: platform_discounts (an Expense, default name Platform Discounts): the part of a discount the platform pays for (charge or invoice metadata list_price and platform_discount) that is larger than its fee; until it is mapped, such a job is held. Optional, any connection: customer_cash_balance (an Other Current Asset, default name Stripe Customer Cash Balance): bank transfers payers sent into their Stripe cash balance that Stripe has not applied to an invoice yet; they are owed back to the payer (Customer Credits) and are not in the Stripe balance, so never Stripe Clearing; until it is mapped, a change in them is held.",
"additionalProperties": false
},
"job_link": {
"type": "string",
"minLength": 1,
"description": "Platform only, for separate charges and transfers: how a transfer finds its charge (its job). transfer_group (default: the transfer and the charge share a transfer_group) or source_transaction (the transfer was created with source_transaction = the charge). Any other value is read as a metadata key, which is not built: every such job is held. Ask the person how their platform links transfers to charges; do not guess."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"timezone": {
"type": "string",
"description": "IANA time zone the periods are cut in, e.g. America/New_York. Default UTC. As with cadence, a change cannot re-book time already booked."
},
"cutoff_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Invoices finalized before this date are legacy: they stay out of Stripe Receivables."
},
"payout_banks": {
"type": "object",
"description": "Stripe payout destination (ba_... from stripe_list_payouts) -> the ledger bank account it pays into.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string",
"minLength": 1
}
},
"revenue_path": {
"enum": [
"ng_summary",
"stripe_revrec"
],
"type": "string",
"description": "Which journal carries Stripe revenue, AR and cash into the ledger: ng_summary (the NumbersGame period summary, default) or stripe_revrec (Stripe Revenue Recognition's journal, booked from Stripe; the NG summary is then refused so nothing posts twice). Decide it with the person at onboarding (stripe_onboarding_assess recommends one)."
},
"business_model": {
"enum": [
"merchant",
"platform",
"connected_account"
],
"type": "string",
"description": "How the business uses Stripe, as the person answered the first onboarding checkpoint question: merchant (sells its own products or services), platform (collects payments for others and pays them out through Stripe, a marketplace; then ask how it is booked and save revenue_policy: agent (recommended): the full payment is held in Provider Payable and only the platform's fee is revenue; or principal: the full sale is revenue and the provider's share a cost (Provider Costs), booked once Stripe shows the provider's share; it needs the platform accounts for its policy and books on the ng_summary path only), or connected_account (gets paid through someone else's platform). Save what the person said, not what the data suggests. Usually it is already chosen on the company page's Stripe card (Standard = merchant, Marketplace / intermediary = platform); stripe_status shows it."
},
"revenue_policy": {
"enum": [
"agent",
"principal"
],
"type": "string",
"description": "Platform only, REQUIRED there (no default): how the platform's payments are booked; until it is set, a platform's periods are needs_setup. agent (recommended): the full payment is held in Provider Payable and only the platform's fee is revenue. principal: the full sale is revenue and the provider's share is a cost (Provider Costs; provider_payable and provider_costs are then required): every payment is held in Provider Payable and transfers reduce it, as under agent; on the same Stripe evidence that releases an agent's fee (an application fee line, a transfer amount set on the payment, or a separate charge's transfers reaching the expected share) the sale is recognised: Cr revenue (the whole sale without tax), Dr Provider Costs (the provider's share), and the fee from Provider Payable (or, on an application fee line, from Stripe Clearing). After recognition a refund takes the provider's part off revenue and Provider Costs, never more than was recognised (a fee the platform keeps stays in revenue); a dispute or failed payment takes the provider's share off them, its fee share going to Chargebacks as under agent, and after the provider was paid puts the provider's share on Due from Providers, with a warning. Principal covers destination charges and separate charges and transfers: an application fee from a direct charge is held for review under principal. It is the accountant's decision (who controls the service: the platform or the provider); ask the person, do not guess. Changing it after periods were booked is allowed and warned: the booked periods stay as they were, and a sale already recognised keeps its treatment for its later refunds, disputes and fee refunds."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"marketplace_tag": {
"anyOf": [
{
"type": "object",
"required": [
"key",
"value"
],
"properties": {
"key": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "The metadata key, e.g. charge_type."
},
"value": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "The value that marks a marketplace payment, e.g. marketplace. Compared exactly."
}
},
"additionalProperties": false
},
{
"type": "null"
}
],
"description": "Platform only, no default: the metadata key and value the platform puts on every marketplace payment and Stripe invoice (e.g. {key: charge_type, value: marketplace}), for a platform that also sells its own products or services through the same Stripe account. Set, a payment or invoice WITHOUT it is the platform's own sale and is booked as for a merchant (revenue, tax to Tax Collected, refunds off revenue, disputes to Chargebacks); one with it follows the marketplace rules (a tagged payment with no provider link is still held under agent). Not set, nothing is told apart: an unlinked payment is held and an invoice is warned about, as before. Read from the invoice for an invoice's payment, otherwise from the charge or its payment intent. Ask the person which metadata their platform writes; do not guess. null removes it. Changing it after periods were booked is allowed and warned."
},
"revrec_accounts": {
"type": "object",
"description": "Stripe Revenue Recognition account names the Rev Rec journal could not resolve (stripe_propose_revrec_journal lists them) -> ledger account id.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string"
}
},
"refund_fee_policy": {
"enum": [
"pro_rata",
"platform_keeps"
],
"type": "string",
"description": "Platform only. When a destination charge that pays the provider a set amount (transfer_data[amount]) is refunded, or a separate charge (separate charges and transfers) is refunded after its fee was released: pro_rata (default) gives back the platform's fee share, in proportion to the refund, through Platform Fee Refunds; platform_keeps books the whole refund against Provider Payable. Application-fee refunds follow Stripe and do not use it. Ask the person; do not guess."
},
"expected_share_key": {
"type": "string",
"minLength": 1,
"description": "Platform only, for separate charges and transfers: the charge metadata key holding the provider's expected share in integer minor units (cents). Default provider_amount; use the platform's own name for it (e.g. provider_share). For a payment of a Stripe invoice the key is read from the invoice when the charge lacks it (Stripe does not copy invoice metadata to the payment). The platform's fee (charge amount - expected share) is released once the job's transfers reach it; a charge without an integer there is held, and the proposal names it."
},
"recognition_timing": {
"enum": [
"stripe_evidence",
"completion_date"
],
"type": "string",
"description": "Platform only: when the platform's fee (agent) or the sale (principal) is recognised. stripe_evidence (default): when Stripe shows it (an application fee, a transfer amount set on the payment, or the provider's share fully paid). completion_date: on an ACCRUAL company, in the period of the job's completion date read from metadata (completion_date_key) on the Stripe invoice the payment paid, else its PaymentIntent, else the charge; a job without a date stays in Provider Payable and is listed; ignored on cash. Set it only when the platform writes that date into Stripe; ask, do not guess. Changing it after periods were booked applies from the first period not yet booked."
},
"completion_date_key": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "Platform, recognition_timing completion_date: the metadata key holding the job's completion date (YYYY-MM-DD in the company's time zone, a timestamp with Z or an offset, or unix seconds). Default job_completed_at; event platforms often use event_date."
},
"provider_account_key": {
"type": "string",
"minLength": 1,
"description": "Platform only, for separate charges and transfers, no default: the metadata key (on the charge, or on the Stripe invoice it pays) naming the provider's connected account (acct_...), e.g. provider_account. When set, a transfer of a job to a different connected account gets a WARNING in the proposal (the provider may have been paid wrongly); nothing is held. Ask the person which key their platform writes; do not guess."
},
"unsettled_warning_days": {
"type": "integer",
"maximum": 3650,
"minimum": 1,
"description": "Platform only, for separate charges and transfers: after how many days a job whose transfers have not reached the provider's expected share gets a WARNING, in the period proposal and in stripe_tie_out P2. Default 30. A warning only: nothing is held for it."
},
"deferred_revenue_account": {
"type": "string",
"description": "Deferred revenue account id (an Other Current Liability). On the ng_summary path it turns on the month-end deferral of multi-month revenue (stripe_propose_deferral_journal); on stripe_revrec, Stripe's DeferredRevenue accounts book to it."
}
}
}
}
},
"annotations": {
"title": "Set Up Stripe Accounts",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
List Stripe payouts (money Stripe sent to, or took from, the company's bank) by arrival date, with status (paid, in_transit, failed...), whether the payout was automatic (only automatic payouts have a transaction breakdown), its destination bank account and whether that destination is mapped to a ledger bank account, and whether NumbersGame has booked it (and how). Amounts are in the payout currency. To book one, use stripe_book_payout. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › from
First arrival date to include, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
Last arrival date to include, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_list_payouts",
"title": "List Stripe Payouts",
"description": "List Stripe payouts (money Stripe sent to, or took from, the company's bank) by arrival date, with status (paid, in_transit, failed...), whether the payout was automatic (only automatic payouts have a transaction breakdown), its destination bank account and whether that destination is mapped to a ledger bank account, and whether NumbersGame has booked it (and how). Amounts are in the payout currency. To book one, use stripe_book_payout. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"from",
"to",
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last arrival date to include, YYYY-MM-DD."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First arrival date to include, YYYY-MM-DD."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "List Stripe Payouts",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
What one Stripe payout is made of: its balance transactions grouped by Stripe reporting category (charge, refund, fee, dispute...), with count, gross, fees and net per category, and whether they add up to the payout amount (`ties`, `difference`). Amounts are integer minor units of the payout currency (cents for USD). Only AUTOMATIC payouts have this breakdown; for a manual or instant payout Stripe cannot say which transactions it contains, and the result says so (linkage: unavailable_manual_payout) rather than guessing from dates. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Explain the meaning of this value, not just its name.
params › payout_id
The payout, po_...
Explain the meaning of this value, not just its name.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_get_payout_breakdown",
"title": "Stripe Payout Breakdown",
"description": "What one Stripe payout is made of: its balance transactions grouped by Stripe reporting category (charge, refund, fee, dispute...), with count, gross, fees and net per category, and whether they add up to the payout amount (`ties`, `difference`). Amounts are integer minor units of the payout currency (cents for USD). Only AUTOMATIC payouts have this breakdown; for a manual or instant payout Stripe cannot say which transactions it contains, and the result says so (linkage: unavailable_manual_payout) rather than guessing from dates. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"payout_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"payout_id": {
"type": "string",
"pattern": "^po_[A-Za-z0-9]+$",
"description": "The payout, po_..."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe Payout Breakdown",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Book one PAID Stripe payout as money moving from Stripe Clearing to the ledger bank account its destination is mapped to. On QuickBooks that is a Transfer from Stripe Clearing to the bank. On Xero, where Stripe Clearing is a current asset account, it is a Receive Money on the bank with one line coded to Stripe Clearing for the payout amount, against the contact Stripe (found by name, created if missing); a negative payout, Stripe debiting the bank, is a Spend Money coded to Stripe Clearing. Never a Xero bank transfer. A Xero Stripe Clearing that is still a Bank account is refused with how to remap it. This is the ONLY way to book a Stripe payout; the period summary never includes payouts. One call does the right thing for the company: if the bank account has an unbooked bank-feed line for the payout, it books that line (so the feed cannot offer it again, and the company's bank-feed booking mode applies -- a held line is posted through the bank booking run once the user says yes (get_booking_run, then post_booking_run), then this is called again to record it); if the bank account has no feed, it creates the transfer (Xero: the Receive or Spend Money) directly, dated the arrival date, with the payout id in the memo -- when the deposit appears on a bank statement it IS this booking, so match it in the reconciliation and never import it as a new deposit; if the account has a feed but the line has not arrived, it books nothing and says to try after the next sync. If the payout would take Stripe Clearing below zero on its arrival date -- the summary that brought the money in is not booked yet -- it books nothing and returns status summary_first naming the summary to book first; when the summaries up to the arrival are already booked and Clearing would still go below zero, summary_first instead names the items those summaries held and did not book (held_items, each with its fix); allow_negative_clearing: true books it anyway. A payout already booked is reported, not booked again. A payout that failed after booking has its transfer (Xero: its Receive or Spend Money) removed. If the ledger does not confirm the write, the payout is HELD (status booking_pending), not retried, so it cannot post twice: check the ledger, then call again with resolve_pending: true. Home currency only for now. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs89/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payout_id
The payout to book, po_...
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › allow_negative_clearing
Book even if Stripe Clearing would go below zero (status summary_first otherwise). Only when the person says so after seeing why.
Clear enough to supply this argument.
params › resolve_pending
Only for a payout whose booking did not confirm (status booking_pending): after checking the ledger for an entry with the payout id in its memo (and deleting it if there is one), pass true to clear the hold and book it once.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_book_payout",
"title": "Book Stripe Payout",
"description": "Book one PAID Stripe payout as money moving from Stripe Clearing to the ledger bank account its destination is mapped to. On QuickBooks that is a Transfer from Stripe Clearing to the bank. On Xero, where Stripe Clearing is a current asset account, it is a Receive Money on the bank with one line coded to Stripe Clearing for the payout amount, against the contact Stripe (found by name, created if missing); a negative payout, Stripe debiting the bank, is a Spend Money coded to Stripe Clearing. Never a Xero bank transfer. A Xero Stripe Clearing that is still a Bank account is refused with how to remap it. This is the ONLY way to book a Stripe payout; the period summary never includes payouts. One call does the right thing for the company: if the bank account has an unbooked bank-feed line for the payout, it books that line (so the feed cannot offer it again, and the company's bank-feed booking mode applies -- a held line is posted through the bank booking run once the user says yes (get_booking_run, then post_booking_run), then this is called again to record it); if the bank account has no feed, it creates the transfer (Xero: the Receive or Spend Money) directly, dated the arrival date, with the payout id in the memo -- when the deposit appears on a bank statement it IS this booking, so match it in the reconciliation and never import it as a new deposit; if the account has a feed but the line has not arrived, it books nothing and says to try after the next sync. If the payout would take Stripe Clearing below zero on its arrival date -- the summary that brought the money in is not booked yet -- it books nothing and returns status summary_first naming the summary to book first; when the summaries up to the arrival are already booked and Clearing would still go below zero, summary_first instead names the items those summaries held and did not book (held_items, each with its fix); allow_negative_clearing: true books it anyway. A payout already booked is reported, not booked again. A payout that failed after booking has its transfer (Xero: its Receive or Spend Money) removed. If the ledger does not confirm the write, the payout is HELD (status booking_pending), not retried, so it cannot post twice: check the ledger, then call again with resolve_pending: true. Home currency only for now. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"payout_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"payout_id": {
"type": "string",
"pattern": "^po_[A-Za-z0-9]+$",
"description": "The payout to book, po_..."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"resolve_pending": {
"type": "boolean",
"description": "Only for a payout whose booking did not confirm (status booking_pending): after checking the ledger for an entry with the payout id in its memo (and deleting it if there is one), pass true to clear the hold and book it once."
},
"allow_negative_clearing": {
"type": "boolean",
"description": "Book even if Stripe Clearing would go below zero (status summary_first otherwise). Only when the person says so after seeing why."
}
}
}
}
},
"annotations": {
"title": "Book Stripe Payout",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Search the Stripe balance transactions (every money movement in the Stripe balance) by date, reporting category, amount or source object. Returns gross, fee and net per transaction, in major units of its currency, with its source id. Use it to explain a number in a period summary or a payout, not to book: bookings go through stripe_propose_period_summary and stripe_book_payout. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs84/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › from
First day to include (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
Last day to include (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › reporting_category
Only this Stripe reporting category: charge, refund, fee, dispute, dispute_reversal, payout, payout_reversal, transfer, ...
Explain the meaning of this value, not just its name.
params › min_amount
Only transactions whose absolute gross amount is at least this, in major units (e.g. 125.50).
Clear enough to supply this argument.
params › max_amount
Only transactions whose absolute gross amount is at most this, in major units.
Clear enough to supply this argument.
params › source
Only the transaction created by this Stripe object: a charge (ch_), refund (re_), dispute (dp_) or payout (po_) id.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_search_transactions",
"title": "Search Stripe Transactions",
"description": "Search the Stripe balance transactions (every money movement in the Stripe balance) by date, reporting category, amount or source object. Returns gross, fee and net per transaction, in major units of its currency, with its source id. Use it to explain a number in a period summary or a payout, not to book: bookings go through stripe_propose_period_summary and stripe_book_payout. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"from",
"to",
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last day to include (UTC), YYYY-MM-DD."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First day to include (UTC), YYYY-MM-DD."
},
"source": {
"type": "string",
"description": "Only the transaction created by this Stripe object: a charge (ch_), refund (re_), dispute (dp_) or payout (po_) id."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"max_amount": {
"type": "number",
"description": "Only transactions whose absolute gross amount is at most this, in major units."
},
"min_amount": {
"type": "number",
"description": "Only transactions whose absolute gross amount is at least this, in major units (e.g. 125.50)."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"reporting_category": {
"type": "string",
"description": "Only this Stripe reporting category: charge, refund, fee, dispute, dispute_reversal, payout, payout_reversal, transfer, ..."
}
}
}
}
},
"annotations": {
"title": "Search Stripe Transactions",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Draft ONE summary journal for a Stripe period, without posting anything. The current period is booked in parts: this drafts the next part, covering the Stripe activity since the last booked part (meta.part shows its window and number). Lines: invoices finalized (Dr Stripe Receivables / Cr revenue and Stripe tax collected), payments collected in Stripe (Dr Stripe Clearing / Cr Stripe Receivables), one-off charges, Stripe fees at gross, refunds, credit notes, disputes, write-offs of invoices marked uncollectible in Stripe (however they were marked) and their later recoveries, and customer credits. Every line is dated by when its event happened, so a period that has ended never changes. A period that has ended and was never booked through NumbersGame says previous_period_reason_required: check the ledger for Stripe totals entered by hand, and pass previous_period_reason when booking. Payouts are NOT in the summary (stripe_book_payout books them). It also returns what it will NOT book, with reasons -- other currencies (only the ledger's home currency is booked), invoices before the AR cutoff, invoices paid outside Stripe (their bank line is booked as a Deposit coded to Stripe Receivables), categories it has no treatment for -- plus checks (balanced; Clearing moves exactly as the Stripe balance did), the read windows used, and any match against an unbooked bank-feed line (a correct summary never touches a bank-fed account; a match means Stripe Clearing is mapped to one). If the ledger is closed for the period, the journal is dated on the first open day and the result says so. On a connection whose business_model is platform (a marketplace that pays others out through Stripe) it needs revenue_policy chosen first (needs_setup until then). Agent (revenue_policy agent; the full payment is held in Provider Payable and only the platform's fee is revenue): collections to Provider Payable, transfers out of it, only the platform's fees as revenue, and the message carries a NOTE saying so and what is not built. With revenue_policy principal (the full sale is revenue and the provider's share is a cost) it holds and releases exactly as agent, on the same Stripe evidence, but the release recognises the whole sale: Cr revenue (the sale without tax), Dr Provider Costs (the provider's share), and the fee from Provider Payable (or, on an application fee line, from Stripe Clearing); after recognition a refund takes the provider's part off revenue and Provider Costs, never more than was recognised (a fee the platform keeps stays in revenue), and a dispute or failed payment the provider's share, its fee share going to Chargebacks as under agent; a refund, loss or fee refund of a sale recognised before an agent/principal switch is booked by the policy it was recognised under; an application fee from a direct charge is held for review; the NOTE says so. Under agent, every Stripe invoice is booked Dr Stripe Receivables / Cr Provider Payable when finalized (never revenue), its refunds and disputes come out of Provider Payable, and when its payment shows no transfer to a provider a WARNING names the invoice and the amount to move to revenue if it is the platform's own sale. With marketplace_tag set (stripe_setup_accounts), a payment or invoice without that metadata is the platform's own sale and books as for a merchant (revenue, tax to Tax Collected, refunds and disputes as a merchant's), under agent and principal; only tagged ones follow the marketplace rules, an invoice keeps the class it was finalized under, and a payment whose tag cannot be read is held. Under agent, with separate charges and transfers, a job's fee is released (Dr Provider Payable / Cr Platform Fee Revenue, job_releases) in the period whose transfer makes the job's transfers reach the provider's expected share (charge metadata, expected_share_key, or the Stripe invoice the charge pays when the charge lacks it); when provider_account_key is set, a job's transfer to another connected account than that metadata names gets a WARNING (nothing is held); after a refund before the provider is paid in full, the platform updates the expected share to the reduced share and the fee released is the payment less the refund less that share (under refund_fee_policy pro_rata the refund's part of the fee goes to Platform Fee Refunds); a job with no link, no valid expected share, transfers above it, a link that cannot be read, a refund before the provider was paid in full whose expected share was not updated, or a dispute or failed payment before then is held (needs_review) with the job named, and its fee stays in Provider Payable; a job read this period whose transfers have not reached the share more than unsettled_warning_days (default 30) after its payment gets a WARNING. A refund, dispute or failed payment on a separate charge is split by what its job had paid the provider by then (Due from Providers for a loss), and the WARNING says what to do. On a company whose Accounting basis is accrual, a second NOTE says NumbersGame books the fee when Stripe shows it, not when a service is done, and that the month-end accrual adjustment is the bookkeeper's (from stripe_provider_payable_report). Pass the NOTE and any WARNING on before booking. Show the bookkeeper the lines and held items; to post, call stripe_book_period_summary with the returned proposal_hash. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › date
Any day in the period to summarise, YYYY-MM-DD. The period is that day (daily cadence) or its calendar month (monthly), cut in the company's configured time zone.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_propose_period_summary",
"title": "Propose Stripe Period Summary",
"description": "Draft ONE summary journal for a Stripe period, without posting anything. The current period is booked in parts: this drafts the next part, covering the Stripe activity since the last booked part (meta.part shows its window and number). Lines: invoices finalized (Dr Stripe Receivables / Cr revenue and Stripe tax collected), payments collected in Stripe (Dr Stripe Clearing / Cr Stripe Receivables), one-off charges, Stripe fees at gross, refunds, credit notes, disputes, write-offs of invoices marked uncollectible in Stripe (however they were marked) and their later recoveries, and customer credits. Every line is dated by when its event happened, so a period that has ended never changes. A period that has ended and was never booked through NumbersGame says previous_period_reason_required: check the ledger for Stripe totals entered by hand, and pass previous_period_reason when booking. Payouts are NOT in the summary (stripe_book_payout books them). It also returns what it will NOT book, with reasons -- other currencies (only the ledger's home currency is booked), invoices before the AR cutoff, invoices paid outside Stripe (their bank line is booked as a Deposit coded to Stripe Receivables), categories it has no treatment for -- plus checks (balanced; Clearing moves exactly as the Stripe balance did), the read windows used, and any match against an unbooked bank-feed line (a correct summary never touches a bank-fed account; a match means Stripe Clearing is mapped to one). If the ledger is closed for the period, the journal is dated on the first open day and the result says so. On a connection whose business_model is platform (a marketplace that pays others out through Stripe) it needs revenue_policy chosen first (needs_setup until then). Agent (revenue_policy agent; the full payment is held in Provider Payable and only the platform's fee is revenue): collections to Provider Payable, transfers out of it, only the platform's fees as revenue, and the message carries a NOTE saying so and what is not built. With revenue_policy principal (the full sale is revenue and the provider's share is a cost) it holds and releases exactly as agent, on the same Stripe evidence, but the release recognises the whole sale: Cr revenue (the sale without tax), Dr Provider Costs (the provider's share), and the fee from Provider Payable (or, on an application fee line, from Stripe Clearing); after recognition a refund takes the provider's part off revenue and Provider Costs, never more than was recognised (a fee the platform keeps stays in revenue), and a dispute or failed payment the provider's share, its fee share going to Chargebacks as under agent; a refund, loss or fee refund of a sale recognised before an agent/principal switch is booked by the policy it was recognised under; an application fee from a direct charge is held for review; the NOTE says so. Under agent, every Stripe invoice is booked Dr Stripe Receivables / Cr Provider Payable when finalized (never revenue), its refunds and disputes come out of Provider Payable, and when its payment shows no transfer to a provider a WARNING names the invoice and the amount to move to revenue if it is the platform's own sale. With marketplace_tag set (stripe_setup_accounts), a payment or invoice without that metadata is the platform's own sale and books as for a merchant (revenue, tax to Tax Collected, refunds and disputes as a merchant's), under agent and principal; only tagged ones follow the marketplace rules, an invoice keeps the class it was finalized under, and a payment whose tag cannot be read is held. Under agent, with separate charges and transfers, a job's fee is released (Dr Provider Payable / Cr Platform Fee Revenue, job_releases) in the period whose transfer makes the job's transfers reach the provider's expected share (charge metadata, expected_share_key, or the Stripe invoice the charge pays when the charge lacks it); when provider_account_key is set, a job's transfer to another connected account than that metadata names gets a WARNING (nothing is held); after a refund before the provider is paid in full, the platform updates the expected share to the reduced share and the fee released is the payment less the refund less that share (under refund_fee_policy pro_rata the refund's part of the fee goes to Platform Fee Refunds); a job with no link, no valid expected share, transfers above it, a link that cannot be read, a refund before the provider was paid in full whose expected share was not updated, or a dispute or failed payment before then is held (needs_review) with the job named, and its fee stays in Provider Payable; a job read this period whose transfers have not reached the share more than unsettled_warning_days (default 30) after its payment gets a WARNING. A refund, dispute or failed payment on a separate charge is split by what its job had paid the provider by then (Due from Providers for a loss), and the WARNING says what to do. On a company whose Accounting basis is accrual, a second NOTE says NumbersGame books the fee when Stripe shows it, not when a service is done, and that the month-end accrual adjustment is the bookkeeper's (from stripe_provider_payable_report). Pass the NOTE and any WARNING on before booking. Show the bookkeeper the lines and held items; to post, call stripe_book_period_summary with the returned proposal_hash. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"date",
"realm_id"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Any day in the period to summarise, YYYY-MM-DD. The period is that day (daily cadence) or its calendar month (monthly), cut in the company's configured time zone."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Propose Stripe Period Summary",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Post an APPROVED Stripe period summary (or the next part of one) as one journal, through the ledger's own journal handling. Call stripe_propose_period_summary first, show it to the bookkeeper, and pass its proposal_hash here once they agree. The summary is recomputed and posted only if it still matches that hash; if Stripe changed since (a late refund, a void), nothing is posted and the new hash is returned for review. The current period is booked IN PARTS: book it as often as you like, and each booking posts only the Stripe activity since the previous part (STR-1A2B-2026-09, then STR-1A2B-2026-09.2, ...), dated that day; once the period has ended, its last part is dated its last day. Repeating a booking posts nothing twice: the same proposal reports the existing journal (QuickBooks DocNumber and Xero narration carry the part id). A PREVIOUS period never booked through NumbersGame needs previous_period_reason on this first call, because it may already hold Stripe totals entered by hand; the proposal says when. A correct summary never matches a bank-feed line. If the proposal reported a bank_feed_match, booking still posts the journal and records that unbooked feed line as booked by it, so the feed does not post the same money again; the result names the line, and reverse_bank_booking releases it (the journal stays). If you have checked that the match is a coincidence, pass not_a_bank_line with the reason and the line is left for the feed. Voids, write-offs and credits are part of the summary and need no separate approval: they already happened in Stripe. Items the proposal held are not posted. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › date
A day in the period, the same one given to stripe_propose_period_summary.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › proposal_hash
The proposal_hash from stripe_propose_period_summary, exactly as returned, after the bookkeeper approved that proposal. For a period still running it ends in -<number>: the moment the proposal ran to.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › not_a_bank_line
Only if the proposal reported a bank_feed_match that you have checked and is a coincidence: the reason. Recorded with the booking, and the feed line is then NOT claimed by this journal. Without a match, leave it out.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › previous_period_reason
Only when the proposal says previous_period_reason_required (a period that has ended and was never booked through NumbersGame): what you checked, e.g. 'no Stripe journal or deposits entered by hand for September'. Recorded with the booking.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_book_period_summary",
"title": "Book Stripe Period Summary",
"description": "Post an APPROVED Stripe period summary (or the next part of one) as one journal, through the ledger's own journal handling. Call stripe_propose_period_summary first, show it to the bookkeeper, and pass its proposal_hash here once they agree. The summary is recomputed and posted only if it still matches that hash; if Stripe changed since (a late refund, a void), nothing is posted and the new hash is returned for review. The current period is booked IN PARTS: book it as often as you like, and each booking posts only the Stripe activity since the previous part (STR-1A2B-2026-09, then STR-1A2B-2026-09.2, ...), dated that day; once the period has ended, its last part is dated its last day. Repeating a booking posts nothing twice: the same proposal reports the existing journal (QuickBooks DocNumber and Xero narration carry the part id). A PREVIOUS period never booked through NumbersGame needs previous_period_reason on this first call, because it may already hold Stripe totals entered by hand; the proposal says when. A correct summary never matches a bank-feed line. If the proposal reported a bank_feed_match, booking still posts the journal and records that unbooked feed line as booked by it, so the feed does not post the same money again; the result names the line, and reverse_bank_booking releases it (the journal stays). If you have checked that the match is a coincidence, pass not_a_bank_line with the reason and the line is left for the feed. Voids, write-offs and credits are part of the summary and need no separate approval: they already happened in Stripe. Items the proposal held are not posted. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"date",
"proposal_hash",
"realm_id"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "A day in the period, the same one given to stripe_propose_period_summary."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"proposal_hash": {
"type": "string",
"pattern": "^[0-9a-f]{16}(-\\d{9,11})?$",
"description": "The proposal_hash from stripe_propose_period_summary, exactly as returned, after the bookkeeper approved that proposal. For a period still running it ends in -<number>: the moment the proposal ran to."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"not_a_bank_line": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only if the proposal reported a bank_feed_match that you have checked and is a coincidence: the reason. Recorded with the booking, and the feed line is then NOT claimed by this journal. Without a match, leave it out."
},
"previous_period_reason": {
"type": "string",
"maxLength": 300,
"minLength": 10,
"description": "Only when the proposal says previous_period_reason_required (a period that has ended and was never booked through NumbersGame): what you checked, e.g. 'no Stripe journal or deposits entered by hand for September'. Recorded with the booking."
}
}
}
}
},
"annotations": {
"title": "Book Stripe Period Summary",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Undo a booked Stripe period summary part: removes its journal from the ledger (QuickBooks deletes it; Xero voids a manual journal, since it cannot delete one), and its Stripe activity goes into the next proposal of that period. Only the LATEST part of a period can be reversed; an earlier one answers which later parts to reverse first. Confirm with the bookkeeper first. A reconciled or closed-period journal is refused by the ledger exactly as with delete_journal_entry. A booking that never confirmed is cleared only with resolve_pending, after the ledger has been checked. The same call reverses or clears a deferral (SDF-) or Revenue Recognition (SRR-) month by its id; a deferral month recorded with nothing to post has no journal, so only its record is cleared. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
params › period_id
The part to reverse, as the booking named it: STR-1A2B-2026-09 for the first part, STR-1A2B-2026-09.2 for the second, ...; or a monthly journal's id: SDF-1A2B-2026-09 (deferral), SRR-1A2B-2026-09 (Stripe Revenue Recognition).
Clear enough to supply this argument.
params › resolve_pending
Only for a booking that never confirmed: after checking the ledger for a journal with this period id in its memo (and deleting it if there is one), pass true to clear the claim.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_reverse_period_summary",
"title": "Reverse Stripe Period Summary",
"description": "Undo a booked Stripe period summary part: removes its journal from the ledger (QuickBooks deletes it; Xero voids a manual journal, since it cannot delete one), and its Stripe activity goes into the next proposal of that period. Only the LATEST part of a period can be reversed; an earlier one answers which later parts to reverse first. Confirm with the bookkeeper first. A reconciled or closed-period journal is refused by the ledger exactly as with delete_journal_entry. A booking that never confirmed is cleared only with resolve_pending, after the ledger has been checked. The same call reverses or clears a deferral (SDF-) or Revenue Recognition (SRR-) month by its id; a deferral month recorded with nothing to post has no journal, so only its record is cleared. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"period_id",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"period_id": {
"type": "string",
"pattern": "^(STR-[A-Z0-9]{1,4}-\\d{4}-\\d{2}(-\\d{2})?(\\.[0-9a-z]+)?|S(DF|RR)-[A-Z0-9]{1,4}-\\d{4}-\\d{2})$",
"description": "The part to reverse, as the booking named it: STR-1A2B-2026-09 for the first part, STR-1A2B-2026-09.2 for the second, ...; or a monthly journal's id: SDF-1A2B-2026-09 (deferral), SRR-1A2B-2026-09 (Stripe Revenue Recognition)."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"resolve_pending": {
"type": "boolean",
"description": "Only for a booking that never confirmed: after checking the ledger for a journal with this period id in its memo (and deleting it if there is one), pass true to clear the claim."
}
}
}
}
},
"annotations": {
"title": "Reverse Stripe Period Summary",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
List the Stripe invoices paid OUTSIDE Stripe in a period (ACH, check, wire -- marked paid out of band in Stripe), and credit notes refunded outside Stripe, for matching to bank lines. These are never Stripe collections: book each bank line as a Deposit coded to Stripe Receivables (Dr Bank / Cr Stripe Receivables) with book_bank_transaction when the company has a bank feed, or the ordinary deposit tools when it does not. The period summary leaves them out so Receivables is relieved once. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › date
Any day in the period, YYYY-MM-DD (same period rules as stripe_propose_period_summary).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_list_out_of_band_payments",
"title": "Stripe Invoices Paid Outside Stripe",
"description": "List the Stripe invoices paid OUTSIDE Stripe in a period (ACH, check, wire -- marked paid out of band in Stripe), and credit notes refunded outside Stripe, for matching to bank lines. These are never Stripe collections: book each bank line as a Deposit coded to Stripe Receivables (Dr Bank / Cr Stripe Receivables) with book_bank_transaction when the company has a bank feed, or the ordinary deposit tools when it does not. The period summary leaves them out so Receivables is relieved once. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"date",
"realm_id"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Any day in the period, YYYY-MM-DD (same period rules as stripe_propose_period_summary)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe Invoices Paid Outside Stripe",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Check that the ledger and Stripe agree, as of now: (1) the ledger's Stripe Receivables balance against open Stripe invoices (finalized on or after the AR cutoff, home currency); (2) the ledger's Stripe Clearing balance against the Stripe balance (available + pending) plus payouts that have left the balance but are not booked yet; (3) paid payouts still not booked after N business days (default 3). Differences are reported with both figures, never fixed. The usual causes are items the period proposals held (other currencies, unhandled categories, pre-cutoff invoices) and unbooked payouts. On a Stripe Connect platform it also returns `marketplace`: P1 Provider Payable is not a debit and no provider is below zero; P2 Provider Payable against the open jobs worked out from Stripe, aged; P3 Platform Fee Revenue less refunds against Stripe's application fees and fee releases; P5 Stripe categories the summary holds. On a platform booked as principal (revenue_policy principal), P1 and P2 are the same (it holds in Provider Payable as agent does); P3 is p3_recognised_sales, the ledger's Revenue against the sales recognised from Stripe's evidence, with a provider_costs check (Provider Costs against the provider's share recognised) and open_jobs_to_accrue (the jobs whose sale is not recognised yet). These are warnings with a way forward each; they do not block booking or the close. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
Resolve the mismatch between this description and its schema constraints.
params › unmatched_after_business_days
List paid payouts still unbooked after this many business days. Default 3.
Resolve the mismatch between this description and its schema constraints.
params › fiscal_year_start_month
Platform connections only: the month the fiscal year starts (1 = January, the default), for the platform fee check.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_tie_out",
"title": "Stripe Tie-Out",
"description": "Check that the ledger and Stripe agree, as of now: (1) the ledger's Stripe Receivables balance against open Stripe invoices (finalized on or after the AR cutoff, home currency); (2) the ledger's Stripe Clearing balance against the Stripe balance (available + pending) plus payouts that have left the balance but are not booked yet; (3) paid payouts still not booked after N business days (default 3). Differences are reported with both figures, never fixed. The usual causes are items the period proposals held (other currencies, unhandled categories, pre-cutoff invoices) and unbooked payouts. On a Stripe Connect platform it also returns `marketplace`: P1 Provider Payable is not a debit and no provider is below zero; P2 Provider Payable against the open jobs worked out from Stripe, aged; P3 Platform Fee Revenue less refunds against Stripe's application fees and fee releases; P5 Stripe categories the summary holds. On a platform booked as principal (revenue_policy principal), P1 and P2 are the same (it holds in Provider Payable as agent does); P3 is p3_recognised_sales, the ledger's Revenue against the sales recognised from Stripe's evidence, with a provider_costs check (Provider Costs against the provider's share recognised) and open_jobs_to_accrue (the jobs whose sale is not recognised yet). These are warnings with a way forward each; they do not block booking or the close. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"fiscal_year_start_month": {
"type": "integer",
"maximum": 12,
"minimum": 1,
"description": "Platform connections only: the month the fiscal year starts (1 = January, the default), for the platform fee check."
},
"unmatched_after_business_days": {
"type": "integer",
"maximum": 30,
"minimum": 1,
"description": "List paid payouts still unbooked after this many business days. Default 3."
}
}
}
}
},
"annotations": {
"title": "Stripe Tie-Out",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
List the Stripe product catalogue: every product (active and inactive unless active_only) with its prices -- amount, currency, one-time or recurring, the billing interval, how many months one bill covers, and multi_month=true where one bill covers more than a month (annual, quarterly, semi-annual: revenue on those must be deferred over the service period, not recognised when invoiced). Use it to map products to income accounts and to decide whether the client needs deferrals. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › active_only
Only active products and prices. Default false: inactive ones are listed too, because old invoices still carry them.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_list_products",
"title": "List Stripe Products",
"description": "List the Stripe product catalogue: every product (active and inactive unless active_only) with its prices -- amount, currency, one-time or recurring, the billing interval, how many months one bill covers, and multi_month=true where one bill covers more than a month (annual, quarterly, semi-annual: revenue on those must be deferred over the service period, not recognised when invoiced). Use it to map products to income accounts and to decide whether the client needs deferrals. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"active_only": {
"type": "boolean",
"description": "Only active products and prices. Default false: inactive ones are listed too, because old invoices still carry them."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "List Stripe Products",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description90/100
Search the client's Stripe invoices by status: drafts, open, overdue, failed payments (automatic collection tried and not succeeded, with the number of attempts and the next retry), uncollectible, paid or void, optionally by creation date and customer. Each invoice has its number, customer, amounts due/paid/remaining, finalization and due date, days overdue and collection method. Reads Stripe only; nothing is booked. Write-offs and payments reach the books through the period summary. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › filter
Which invoices: drafts (not finalized), open, overdue (open and past due), failed_payments (Stripe tried to charge automatically and has not succeeded), uncollectible, paid, void, or all. Default all.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › from
Only invoices created on or after this day (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
Only invoices created on or before this day (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › customer
Only this Stripe customer (cus_...).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_search_invoices",
"title": "Search Stripe Invoices",
"description": "Search the client's Stripe invoices by status: drafts, open, overdue, failed payments (automatic collection tried and not succeeded, with the number of attempts and the next retry), uncollectible, paid or void, optionally by creation date and customer. Each invoice has its number, customer, amounts due/paid/remaining, finalization and due date, days overdue and collection method. Reads Stripe only; nothing is booked. Write-offs and payments reach the books through the period summary. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only invoices created on or before this day (UTC), YYYY-MM-DD."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only invoices created on or after this day (UTC), YYYY-MM-DD."
},
"filter": {
"enum": [
"all",
"drafts",
"open",
"overdue",
"failed_payments",
"uncollectible",
"paid",
"void"
],
"type": "string",
"description": "Which invoices: drafts (not finalized), open, overdue (open and past due), failed_payments (Stripe tried to charge automatically and has not succeeded), uncollectible, paid, void, or all. Default all."
},
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$",
"description": "Only this Stripe customer (cus_...)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Search Stripe Invoices",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Age what Stripe customers owe, as of now: open Stripe invoices by customer in buckets current / 1-30 / 31-60 / 61-90 / over 90 days past due (due date, or finalization when there is none). The total is compared with the ledger's Stripe Receivables balance -- the books carry Stripe AR as that one balance, so the ledger's own AR aging does not show it; this is its aging. Invoices outside Stripe Receivables (other currencies, finalized before the AR cutoff) are listed apart, not mixed in. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
Describe the returned information so the agent knows whether it will answer the request.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_ar_aging",
"title": "Stripe AR Aging",
"description": "Age what Stripe customers owe, as of now: open Stripe invoices by customer in buckets current / 1-30 / 31-60 / 61-90 / over 90 days past due (due date, or finalization when there is none). The total is compared with the ledger's Stripe Receivables balance -- the books carry Stripe AR as that one balance, so the ledger's own AR aging does not show it; this is its aging. Invoices outside Stripe Receivables (other currencies, finalized before the AR cutoff) are listed apart, not mixed in. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe AR Aging",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
For a Stripe Connect platform (marketplace): what is still owed to each provider, per provider and per job, worked out from Stripe for a date. Each job (a charge and the transfers, refunds and disputes that point to it) shows collected, transferred, refunded, losses, fee released and open, with its Stripe ids; Stripe invoices not yet paid or paid outside Stripe are listed apart, and a principal platform also gets the open jobs to accrue (those whose sale is not recognised yet). Use it to see which providers and jobs make up the ledger's Provider Payable, or when stripe_tie_out's P1 or P2 check reports a difference -- the books carry Provider Payable as one balance, with no provider detail on the ledger lines. It reads Stripe, not the ledger (only the ledger's home currency); stripe_tie_out compares the total with the ledger. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › as_of
YYYY-MM-DD: Stripe activity up to the end of this day (UTC). Default today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_provider_payable_report",
"title": "Stripe Provider Payable Report",
"description": "For a Stripe Connect platform (marketplace): what is still owed to each provider, per provider and per job, worked out from Stripe for a date. Each job (a charge and the transfers, refunds and disputes that point to it) shows collected, transferred, refunded, losses, fee released and open, with its Stripe ids; Stripe invoices not yet paid or paid outside Stripe are listed apart, and a principal platform also gets the open jobs to accrue (those whose sale is not recognised yet). Use it to see which providers and jobs make up the ledger's Provider Payable, or when stripe_tie_out's P1 or P2 check reports a difference -- the books carry Provider Payable as one balance, with no provider detail on the ledger lines. It reads Stripe, not the ledger (only the ledger's home currency); stripe_tie_out compares the total with the ledger. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"as_of": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD: Stripe activity up to the end of this day (UTC). Default today."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe Provider Payable Report",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description92/100
List the client's Stripe subscriptions -- customer, status, start, collection method, payment terms, and per item the product, price, amount per bill, interval and current period -- with set-up flags: multi-month billing (needs deferral), invoices sent without payment terms, Stripe Tax off, cancelling at period end. Pass expected_deals to check that new deals are set up in Stripe as agreed: each deal comes back as matches, different (with what differs), missing, or ambiguous. Reads only; nothing is changed in Stripe. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › status
Only subscriptions in this status. Default all (Stripe's 'all' includes canceled).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › from
Only subscriptions created on or after this day (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › to
Only subscriptions created on or before this day (UTC), YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › customer
Only this Stripe customer (cus_...).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › expected_deals › items › customer
Customer name as the deal list has it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › expected_deals › items › amount
Amount per bill, all items together, in major units.
Clear enough to supply this argument.
params › expected_deals › items › interval
How often it is billed.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › expected_deals › items › product
Product name, if the deal names one.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_list_subscriptions",
"title": "List Stripe Subscriptions",
"description": "List the client's Stripe subscriptions -- customer, status, start, collection method, payment terms, and per item the product, price, amount per bill, interval and current period -- with set-up flags: multi-month billing (needs deferral), invoices sent without payment terms, Stripe Tax off, cancelling at period end. Pass expected_deals to check that new deals are set up in Stripe as agreed: each deal comes back as matches, different (with what differs), missing, or ambiguous. Reads only; nothing is changed in Stripe. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only subscriptions created on or before this day (UTC), YYYY-MM-DD."
},
"from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Only subscriptions created on or after this day (UTC), YYYY-MM-DD."
},
"status": {
"enum": [
"all",
"active",
"trialing",
"past_due",
"canceled",
"unpaid",
"incomplete",
"paused"
],
"type": "string",
"description": "Only subscriptions in this status. Default all (Stripe's 'all' includes canceled)."
},
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$",
"description": "Only this Stripe customer (cus_...)."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"expected_deals": {
"type": "array",
"items": {
"type": "object",
"required": [
"customer"
],
"properties": {
"amount": {
"type": "number",
"description": "Amount per bill, all items together, in major units."
},
"product": {
"type": "string",
"description": "Product name, if the deal names one."
},
"customer": {
"type": "string",
"minLength": 1,
"description": "Customer name as the deal list has it."
},
"interval": {
"enum": [
"month",
"quarter",
"year",
"one_time"
],
"type": "string",
"description": "How often it is billed."
}
},
"additionalProperties": false
},
"maxItems": 500,
"description": "Deals to check against Stripe (from a CRM export or a contract list the person gives you). Each is matched by customer name, then amount, interval and product are compared."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "List Stripe Subscriptions",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
The company's Stripe revenue mappings (the Stripe connector's bank rules): which income account, and optionally which class, each Stripe product or price books into in the period summary. A price rule beats a product rule; anything without a rule books to the default Revenue account from stripe_setup_accounts. With include_products (default), every price is listed with the account it books to, and active prices still on the default are counted, so unmapped revenue is seen before booking. Call this before proposing a mapping; save rules with stripe_upsert_revenue_mapping and remove one with stripe_remove_revenue_mapping. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › include_products
Also read every Stripe price and say which account its revenue books to (a rule, or the default Revenue account). Default true.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_get_revenue_mappings",
"title": "Get Stripe Revenue Mappings",
"description": "The company's Stripe revenue mappings (the Stripe connector's bank rules): which income account, and optionally which class, each Stripe product or price books into in the period summary. A price rule beats a product rule; anything without a rule books to the default Revenue account from stripe_setup_accounts. With include_products (default), every price is listed with the account it books to, and active prices still on the default are counted, so unmapped revenue is seen before booking. Call this before proposing a mapping; save rules with stripe_upsert_revenue_mapping and remove one with stripe_remove_revenue_mapping. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"include_products": {
"type": "boolean",
"description": "Also read every Stripe price and say which account its revenue books to (a rule, or the default Revenue account). Default true."
}
}
}
}
},
"annotations": {
"title": "Get Stripe Revenue Mappings",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Save one Stripe revenue mapping: the income account, and optionally the class, that revenue on a Stripe product or price books to in the period summary. Propose mappings to the person first and save only what they agree to. The rule is checked before saving -- the Stripe product or price must exist, the account must be an active income account, the class must exist -- and any problem is reported with nothing saved. Saving again for the same id replaces the rule; to delete one, use stripe_remove_revenue_mapping. Summaries already booked keep the accounts they were booked with; the rule applies from the next proposal. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs91/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › kind
Map a whole Stripe product (prod_...) or one price (price_...). A price rule beats its product's rule.
Clear enough to supply this argument.
params › id
The Stripe product or price id, from stripe_list_products.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › account_id
The ledger income account id its revenue books to (search_accounts).
Clear enough to supply this argument.
params › class_id
Optional class to put on the revenue line: a QuickBooks class id, or on Xero the tracking option id (search_classes). Ask the person; never infer it.
Clear enough to supply this argument.
params › notes
Why this mapping, in a sentence the next reviewer can read.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › confidence
high only when the person confirmed this mapping; default low.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_upsert_revenue_mapping",
"title": "Save Stripe Revenue Mapping",
"description": "Save one Stripe revenue mapping: the income account, and optionally the class, that revenue on a Stripe product or price books to in the period summary. Propose mappings to the person first and save only what they agree to. The rule is checked before saving -- the Stripe product or price must exist, the account must be an active income account, the class must exist -- and any problem is reported with nothing saved. Saving again for the same id replaces the rule; to delete one, use stripe_remove_revenue_mapping. Summaries already booked keep the accounts they were booked with; the rule applies from the next proposal. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"kind",
"id",
"account_id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(prod|price)_[A-Za-z0-9]+$",
"description": "The Stripe product or price id, from stripe_list_products."
},
"kind": {
"enum": [
"product",
"price"
],
"type": "string",
"description": "Map a whole Stripe product (prod_...) or one price (price_...). A price rule beats its product's rule."
},
"notes": {
"type": "string",
"maxLength": 500,
"description": "Why this mapping, in a sentence the next reviewer can read."
},
"class_id": {
"type": "string",
"description": "Optional class to put on the revenue line: a QuickBooks class id, or on Xero the tracking option id (search_classes). Ask the person; never infer it."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"account_id": {
"type": "string",
"minLength": 1,
"description": "The ledger income account id its revenue books to (search_accounts)."
},
"confidence": {
"enum": [
"high",
"low"
],
"type": "string",
"description": "high only when the person confirmed this mapping; default low."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Save Stripe Revenue Mapping",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Delete ONE saved Stripe revenue mapping (stripe_get_revenue_mappings lists them), after the person agreed. From the next summary its revenue books under the product's rule (when a price rule is removed) or the setup's default Revenue account. Summaries already booked keep the accounts they were booked with. Removes nothing in the ledger or in Stripe. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs94/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › kind
Whether the rule is on a whole Stripe product (prod_...) or one price (price_...), as stripe_get_revenue_mappings lists it.
Clear enough to supply this argument.
params › id
The Stripe product or price id whose rule to remove.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_remove_revenue_mapping",
"title": "Remove Stripe Revenue Mapping",
"description": "Delete ONE saved Stripe revenue mapping (stripe_get_revenue_mappings lists them), after the person agreed. From the next summary its revenue books under the product's rule (when a price rule is removed) or the setup's default Revenue account. Summaries already booked keep the accounts they were booked with. Removes nothing in the ledger or in Stripe. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"kind",
"id",
"realm_id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^(prod|price)_[A-Za-z0-9]+$",
"description": "The Stripe product or price id whose rule to remove."
},
"kind": {
"enum": [
"product",
"price"
],
"type": "string",
"description": "Whether the rule is on a whole Stripe product (prod_...) or one price (price_...), as stripe_get_revenue_mappings lists it."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Remove Stripe Revenue Mapping",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Build the CSV for Stripe Revenue Recognition's bulk chart-of-accounts mapping from this company's Stripe setup and revenue mappings, with every GL account named exactly as the ledger shows it (QuickBooks Parent:Child) and its number, so Stripe's reports and the books use the same accounts. Rows: AccountsReceivable, Cash, PendingCash, Revenue, TaxLiability, Fees, BadDebt, Disputes and customer balances from the mapped slots, plus one Revenue row per product or price rule. Unmapped slots are left out and listed. Stripe has no API for this mapping: give the person the CSV to upload in the Stripe Dashboard (Revenue Recognition > Chart of accounts > Map chart of accounts > Upload CSV) and ask for Stripe's error file if rows fail. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
Effective Start Date for every row, YYYY-MM-DD. Default: the connection's AR cutoff (start) date.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_revrec_mapping_csv",
"title": "Stripe Rev Rec Mapping CSV",
"description": "Build the CSV for Stripe Revenue Recognition's bulk chart-of-accounts mapping from this company's Stripe setup and revenue mappings, with every GL account named exactly as the ledger shows it (QuickBooks Parent:Child) and its number, so Stripe's reports and the books use the same accounts. Rows: AccountsReceivable, Cash, PendingCash, Revenue, TaxLiability, Fees, BadDebt, Disputes and customer balances from the mapped slots, plus one Revenue row per product or price rule. Unmapped slots are left out and listed. Stripe has no API for this mapping: give the person the CSV to upload in the Stripe Dashboard (Revenue Recognition > Chart of accounts > Map chart of accounts > Upload CSV) and ask for Stripe's error file if rows fail. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Effective Start Date for every row, YYYY-MM-DD. Default: the connection's AR cutoff (start) date."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe Rev Rec Mapping CSV",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Start (or check) the Stripe onboarding for a company, in one read: what is already set up and missing, candidate ledger accounts for each missing slot (Stripe-named first), misuse flags (Clearing on a fed account, Stripe AR on the ledger's own A/R, on Xero a bank account fed by Xero's own Stripe connection), the product catalogue with multi-month prices (deferrals) and active prices without a revenue rule, whether Stripe Revenue Recognition answers on this account, how Stripe deposits were booked in the last 60 days (QuickBooks), and the recommended revenue path with its reason. Also reads whether the Stripe account shows Stripe Connect platform activity (transfers to connected accounts or application fees: a marketplace platform), as a hint; selling through someone else's platform cannot be seen this way. Candidates already mapped to another Stripe slot are marked already_used_for and listed last. Returns the checkpoint questions to ask the person ONE AT A TIME (how the business uses Stripe, asked first, and only when it was not already chosen on the company page's Stripe card; on a marketplace, agent or principal right after it, recommending agent, then, while not yet saved, how a transfer finds its charge (job_link), the metadata key with the provider's expected share (expected_share_key) and, except under principal, what a refund does to the platform's fee (refund_fee_policy), each naming its default and recommending it; Rev Rec on? multi-month billing? start date?) and the next steps. On a marketplace platform the reply also gives the company's Accounting basis (accounting_basis: cash, accrual, or null when not set on the company page) and accounting_basis_note, which says what NumbersGame books on that basis and, on accrual, the month-end adjustment the bookkeeper books from stripe_provider_payable_report: pass it on. Offer this when stripe_status says a connection is not onboarded. Reads only; nothing is created or saved. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs97/100
Input documentation gives an agent enough context to populate the arguments.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_onboarding_assess",
"title": "Assess Stripe Onboarding",
"description": "Start (or check) the Stripe onboarding for a company, in one read: what is already set up and missing, candidate ledger accounts for each missing slot (Stripe-named first), misuse flags (Clearing on a fed account, Stripe AR on the ledger's own A/R, on Xero a bank account fed by Xero's own Stripe connection), the product catalogue with multi-month prices (deferrals) and active prices without a revenue rule, whether Stripe Revenue Recognition answers on this account, how Stripe deposits were booked in the last 60 days (QuickBooks), and the recommended revenue path with its reason. Also reads whether the Stripe account shows Stripe Connect platform activity (transfers to connected accounts or application fees: a marketplace platform), as a hint; selling through someone else's platform cannot be seen this way. Candidates already mapped to another Stripe slot are marked already_used_for and listed last. Returns the checkpoint questions to ask the person ONE AT A TIME (how the business uses Stripe, asked first, and only when it was not already chosen on the company page's Stripe card; on a marketplace, agent or principal right after it, recommending agent, then, while not yet saved, how a transfer finds its charge (job_link), the metadata key with the provider's expected share (expected_share_key) and, except under principal, what a refund does to the platform's fee (refund_fee_policy), each naming its default and recommending it; Rev Rec on? multi-month billing? start date?) and the next steps. On a marketplace platform the reply also gives the company's Accounting basis (accounting_basis: cash, accrual, or null when not set on the company page) and accounting_basis_note, which says what NumbersGame books on that basis and, on accrual, the month-end adjustment the bookkeeper books from stripe_provider_payable_report: pass it on. Offer this when stripe_status says a connection is not onboarded. Reads only; nothing is created or saved. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Assess Stripe Onboarding",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
What the ledger should carry for Stripe the moment the connector starts, against what it carries, and a PROPOSED opening entry with a reason per line: open Stripe AR at the start (to the legacy receivables account, where the connector books those invoices' later payments), money in Stripe at the start (balance plus payouts on their way) against Stripe Clearing, and deferred revenue on multi-month lines invoiced before the start. Offsets assume the ledger booked Stripe on a cash or payout basis before the start: current-year amounts to revenue, earlier years to retained earnings; Clearing differences are marked for review. Posts NOTHING: show the person every line, and post it with create_journal_entry dated the day before the start only after they approve. Customer credit balances are Stripe's current ones (Stripe keeps no history of them). Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › start_date
The date Stripe accruals start (the AR cutoff), YYYY-MM-DD. Balances are taken at 00:00 on it, in the connection's time zone.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › fiscal_year_start_month
Month the fiscal year starts, 1-12. Default 1 (January). Decides current-year revenue vs retained earnings.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › deferred_revenue_account_id
The ledger's deferred revenue account (Other Current Liability), to include deferred revenue at the start.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › retained_earnings_account_id
The ledger's retained earnings account, the offset for amounts from earlier fiscal years (search_accounts).
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_opening_balances",
"title": "Stripe Opening Balances",
"description": "What the ledger should carry for Stripe the moment the connector starts, against what it carries, and a PROPOSED opening entry with a reason per line: open Stripe AR at the start (to the legacy receivables account, where the connector books those invoices' later payments), money in Stripe at the start (balance plus payouts on their way) against Stripe Clearing, and deferred revenue on multi-month lines invoiced before the start. Offsets assume the ledger booked Stripe on a cash or payout basis before the start: current-year amounts to revenue, earlier years to retained earnings; Clearing differences are marked for review. Posts NOTHING: show the person every line, and post it with create_journal_entry dated the day before the start only after they approve. Customer credit balances are Stripe's current ones (Stripe keeps no history of them). Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"start_date",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The date Stripe accruals start (the AR cutoff), YYYY-MM-DD. Balances are taken at 00:00 on it, in the connection's time zone."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"fiscal_year_start_month": {
"type": "integer",
"maximum": 12,
"minimum": 1,
"description": "Month the fiscal year starts, 1-12. Default 1 (January). Decides current-year revenue vs retained earnings."
},
"deferred_revenue_account_id": {
"type": "string",
"description": "The ledger's deferred revenue account (Other Current Liability), to include deferred revenue at the start."
},
"retained_earnings_account_id": {
"type": "string",
"description": "The ledger's retained earnings account, the offset for amounts from earlier fiscal years (search_accounts)."
}
}
}
}
},
"annotations": {
"title": "Stripe Opening Balances",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Draft the month-end deferral journal for one ended month and show it; posts nothing. The period summary credits revenue in full when a Stripe invoice is finalized; for lines billed for more than a month (annual, quarterly, multi-month) that is too early. This month-end journal moves what is not yet earned to the deferred revenue account and releases what was earned in the month, per revenue mapping (same accounts and classes as the summary), computed from each line's service period in Stripe. For the ng_summary revenue path with a deferred revenue account set (stripe_setup_accounts); months are booked in order from the start date. A month with nothing to defer or release posts no journal: its proposal still carries a proposal_hash, and booking that records the month as done (nothing is posted), so the next month can follow. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › month
The month, YYYY-MM.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_propose_deferral_journal",
"title": "Propose Stripe Deferral Journal",
"description": "Draft the month-end deferral journal for one ended month and show it; posts nothing. The period summary credits revenue in full when a Stripe invoice is finalized; for lines billed for more than a month (annual, quarterly, multi-month) that is too early. This month-end journal moves what is not yet earned to the deferred revenue account and releases what was earned in the month, per revenue mapping (same accounts and classes as the summary), computed from each line's service period in Stripe. For the ng_summary revenue path with a deferred revenue account set (stripe_setup_accounts); months are booked in order from the start date. A month with nothing to defer or release posts no journal: its proposal still carries a proposal_hash, and booking that records the month as done (nothing is posted), so the next month can follow. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"month",
"realm_id"
],
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, YYYY-MM."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Propose Stripe Deferral Journal",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Post the month-end deferral journal the person approved, by its proposal_hash. It is recomputed first: if it changed, nothing posts and the new hash is returned. A month posts once. If the ledger does not confirm the write, the month is HELD, not retried: check the ledger for the journal, then clear the hold with stripe_reverse_period_summary (resolve_pending) if it is not there. The period summary credits revenue in full when a Stripe invoice is finalized; for lines billed for more than a month (annual, quarterly, multi-month) that is too early. This month-end journal moves what is not yet earned to the deferred revenue account and releases what was earned in the month, per revenue mapping (same accounts and classes as the summary), computed from each line's service period in Stripe. For the ng_summary revenue path with a deferred revenue account set (stripe_setup_accounts); months are booked in order from the start date. A month with nothing to defer or release posts no journal: its proposal still carries a proposal_hash, and booking that records the month as done (nothing is posted), so the next month can follow. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
Describe the returned information so the agent knows whether it will answer the request.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › month
The month, YYYY-MM.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › proposal_hash
From stripe_propose_deferral_journal, after the person approved it.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_book_deferral_journal",
"title": "Book Stripe Deferral Journal",
"description": "Post the month-end deferral journal the person approved, by its proposal_hash. It is recomputed first: if it changed, nothing posts and the new hash is returned. A month posts once. If the ledger does not confirm the write, the month is HELD, not retried: check the ledger for the journal, then clear the hold with stripe_reverse_period_summary (resolve_pending) if it is not there. The period summary credits revenue in full when a Stripe invoice is finalized; for lines billed for more than a month (annual, quarterly, multi-month) that is too early. This month-end journal moves what is not yet earned to the deferred revenue account and releases what was earned in the month, per revenue mapping (same accounts and classes as the summary), computed from each line's service period in Stripe. For the ng_summary revenue path with a deferred revenue account set (stripe_setup_accounts); months are booked in order from the start date. A month with nothing to defer or release posts no journal: its proposal still carries a proposal_hash, and booking that records the month as done (nothing is posted), so the next month can follow. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"month",
"proposal_hash",
"realm_id"
],
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, YYYY-MM."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"proposal_hash": {
"type": "string",
"minLength": 1,
"description": "From stripe_propose_deferral_journal, after the person approved it."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Book Stripe Deferral Journal",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Draft Stripe Revenue Recognition's journal for one ended month and show it; posts nothing. For the stripe_revrec revenue path (the client uses Stripe Revenue Recognition): reads Stripe's debits-and-credits journal for the month from Stripe's Reporting API (beta) -- the first call asks Stripe to build it and says to call again -- maps each Stripe account to a ledger account (GL code, ledger name, revrec_accounts, or Stripe's default account through the setup's slots; anything unresolved is listed and nothing is booked), and dates it the month's last day. It replaces exporting the journal from Stripe and importing it by hand. The NumbersGame period summary is never booked on this path. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › month
The month, YYYY-MM.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › allow_open_period
Book even though Stripe still marks the month an open accounting period (its entries can change). Only when the person says so.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_propose_revrec_journal",
"title": "Propose Stripe Rev Rec Journal",
"description": "Draft Stripe Revenue Recognition's journal for one ended month and show it; posts nothing. For the stripe_revrec revenue path (the client uses Stripe Revenue Recognition): reads Stripe's debits-and-credits journal for the month from Stripe's Reporting API (beta) -- the first call asks Stripe to build it and says to call again -- maps each Stripe account to a ledger account (GL code, ledger name, revrec_accounts, or Stripe's default account through the setup's slots; anything unresolved is listed and nothing is booked), and dates it the month's last day. It replaces exporting the journal from Stripe and importing it by hand. The NumbersGame period summary is never booked on this path. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"month",
"realm_id"
],
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, YYYY-MM."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"allow_open_period": {
"type": "boolean",
"description": "Book even though Stripe still marks the month an open accounting period (its entries can change). Only when the person says so."
}
}
}
}
},
"annotations": {
"title": "Propose Stripe Rev Rec Journal",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Post Stripe Revenue Recognition's journal for a month the person approved, by its proposal_hash; recomputed first, posted once. Refused on a connection that books the NumbersGame summary (revenue_path ng_summary). For the stripe_revrec revenue path (the client uses Stripe Revenue Recognition): reads Stripe's debits-and-credits journal for the month from Stripe's Reporting API (beta) -- the first call asks Stripe to build it and says to call again -- maps each Stripe account to a ledger account (GL code, ledger name, revrec_accounts, or Stripe's default account through the setup's slots; anything unresolved is listed and nothing is booked), and dates it the month's last day. It replaces exporting the journal from Stripe and importing it by hand. The NumbersGame period summary is never booked on this path. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › month
The month, YYYY-MM.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › proposal_hash
From stripe_propose_revrec_journal, after the person approved it.
Clear enough to supply this argument.
params › allow_open_period
Book even though Stripe still marks the month an open accounting period (its entries can change). Only when the person says so.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_book_revrec_journal",
"title": "Book Stripe Rev Rec Journal",
"description": "Post Stripe Revenue Recognition's journal for a month the person approved, by its proposal_hash; recomputed first, posted once. Refused on a connection that books the NumbersGame summary (revenue_path ng_summary). For the stripe_revrec revenue path (the client uses Stripe Revenue Recognition): reads Stripe's debits-and-credits journal for the month from Stripe's Reporting API (beta) -- the first call asks Stripe to build it and says to call again -- maps each Stripe account to a ledger account (GL code, ledger name, revrec_accounts, or Stripe's default account through the setup's slots; anything unresolved is listed and nothing is booked), and dates it the month's last day. It replaces exporting the journal from Stripe and importing it by hand. The NumbersGame period summary is never booked on this path. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"month",
"proposal_hash",
"realm_id"
],
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "The month, YYYY-MM."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"proposal_hash": {
"type": "string",
"minLength": 1,
"description": "From stripe_propose_revrec_journal, after the person approved it."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"allow_open_period": {
"type": "boolean",
"description": "Book even though Stripe still marks the month an open accounting period (its entries can change). Only when the person says so."
}
}
}
}
},
"annotations": {
"title": "Book Stripe Rev Rec Journal",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Find which open Stripe invoice(s) a payment received OUTSIDE Stripe pays: a wire or ACH into the client's bank. Ranks candidates by a remembered payer (learned from earlier confirmed matches), the customer's name in the payer text, an exact amount on one invoice, several of one customer's invoices adding up to the amount, or a partial payment. Never picks between two customers it cannot tell apart: they are listed side by side, low confidence. Show the candidates to the person; apply the one they choose with stripe_apply_outside_payment. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs85/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › amount
The payment as it reached the bank, in major units.
Clear enough to supply this argument.
params › payer
The payer text on the bank line (name, reference).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › date
The bank line's date, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_match_payment",
"title": "Match Payment to Stripe Invoices",
"description": "Find which open Stripe invoice(s) a payment received OUTSIDE Stripe pays: a wire or ACH into the client's bank. Ranks candidates by a remembered payer (learned from earlier confirmed matches), the customer's name in the payer text, an exact amount on one invoice, several of one customer's invoices adding up to the amount, or a partial payment. Never picks between two customers it cannot tell apart: they are listed side by side, low confidence. Show the candidates to the person; apply the one they choose with stripe_apply_outside_payment. Reads only. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"amount",
"payer",
"realm_id"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The bank line's date, YYYY-MM-DD."
},
"payer": {
"type": "string",
"minLength": 1,
"description": "The payer text on the bank line (name, reference)."
},
"amount": {
"type": "number",
"description": "The payment as it reached the bank, in major units.",
"exclusiveMinimum": 0
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Match Payment to Stripe Invoices",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Apply a payment received outside Stripe (wire, ACH, check) to the open Stripe invoice(s) it pays: marks a fully paid invoice paid outside Stripe in Stripe, books the bank side Dr bank / Cr Stripe Receivables (on the bank-feed line when plaid_transaction_id is given, else as a deposit on bank_account_id), and remembers the payer for next time. A partial payment is booked in the ledger and left for the person to record on the invoice in the Stripe Dashboard. Use stripe_match_payment first to find the invoices. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs92/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › invoices
The invoice(s) the payment pays, all one customer's.
Clear enough to supply this argument.
params › amount
The payment, major units.
Clear enough to supply this argument.
params › date
The bank line's date, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › payer
The payer text on the bank line; remembered for the next match.
Clear enough to supply this argument.
params › plaid_transaction_id
The bank-feed line, if the bank has a NumbersGame feed (search_plaid_transactions).
Clear enough to supply this argument.
params › bank_account_id
Without a feed: the ledger bank account the money reached.
Clear enough to supply this argument.
params › learn_alias
Remember the payer text for this customer. Default true.
Clear enough to supply this argument.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_apply_outside_payment",
"title": "Apply Payment Received Outside Stripe",
"description": "Apply a payment received outside Stripe (wire, ACH, check) to the open Stripe invoice(s) it pays: marks a fully paid invoice paid outside Stripe in Stripe, books the bank side Dr bank / Cr Stripe Receivables (on the bank-feed line when plaid_transaction_id is given, else as a deposit on bank_account_id), and remembers the payer for next time. A partial payment is booked in the ledger and left for the person to record on the invoice in the Stripe Dashboard. Use stripe_match_payment first to find the invoices. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoices",
"amount",
"date",
"realm_id"
],
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The bank line's date, YYYY-MM-DD."
},
"payer": {
"type": "string",
"description": "The payer text on the bank line; remembered for the next match."
},
"amount": {
"type": "number",
"description": "The payment, major units.",
"exclusiveMinimum": 0
},
"invoices": {
"type": "array",
"items": {
"type": "string",
"pattern": "^in_[A-Za-z0-9]+$"
},
"maxItems": 50,
"minItems": 1,
"description": "The invoice(s) the payment pays, all one customer's."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"learn_alias": {
"type": "boolean",
"description": "Remember the payer text for this customer. Default true."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"bank_account_id": {
"type": "string",
"description": "Without a feed: the ledger bank account the money reached."
},
"plaid_transaction_id": {
"type": "string",
"description": "The bank-feed line, if the bank has a NumbersGame feed (search_plaid_transactions)."
}
}
}
}
},
"annotations": {
"title": "Apply Payment Received Outside Stripe",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Mark an open Stripe invoice uncollectible (write it off) in Stripe. The next period summary books Dr Bad debt / Cr Stripe Receivables for what was still owed; an invoice from before the start date is held for the opening balances instead, and the preview says which. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
3 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › invoice
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_mark_invoice_uncollectible",
"title": "Mark Stripe Invoice Uncollectible",
"description": "Mark an open Stripe invoice uncollectible (write it off) in Stripe. The next period summary books Dr Bad debt / Cr Stripe Receivables for what was still owed; an invoice from before the start date is held for the opening balances instead, and the preview says which. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice",
"realm_id"
],
"properties": {
"invoice": {
"type": "string",
"pattern": "^in_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Mark Stripe Invoice Uncollectible",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Void an open or uncollectible Stripe invoice in Stripe: cancel it, keeping its number and paper trail. Stripe refuses a draft (deleted, not voided), a paid invoice (use a credit note) and an invoice with an open or paid payment on it; the preview says so before anything is sent. The books follow through the next period summary: Dr Revenue and Sales tax / Cr Stripe Receivables for what was still owed, nothing when it was finalized in the same period or already written off, held for the opening balances when it is from before the start date. Voiding a subscription's invoice does not cancel the subscription. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs69/100
3 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › invoice
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_void_invoice",
"title": "Void Stripe Invoice",
"description": "Void an open or uncollectible Stripe invoice in Stripe: cancel it, keeping its number and paper trail. Stripe refuses a draft (deleted, not voided), a paid invoice (use a credit note) and an invoice with an open or paid payment on it; the preview says so before anything is sent. The books follow through the next period summary: Dr Revenue and Sales tax / Cr Stripe Receivables for what was still owed, nothing when it was finalized in the same period or already written off, held for the opening balances when it is from before the start date. Voiding a subscription's invoice does not cancel the subscription. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice",
"realm_id"
],
"properties": {
"invoice": {
"type": "string",
"pattern": "^in_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Void Stripe Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Create a customer in the client's Stripe account. The preview warns when Stripe already has a customer with that email. Nothing is created in the books. An email address set on a Stripe customer through NumbersGame is one Stripe will email invoices to, so a subscription for that customer is held (recipient_unconfirmed, nothing changed in Stripe) until a person confirms the address once in NumbersGame (Firm settings → Document sending → Recipients (or, for a firm without document sending, Firm settings → Stripe customer emails)) with a password or passkey; then call it again. No parameter skips this. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
3 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › name
Not provided
Missing description. Explain what this value means and how to supply it.
params › email
Not provided
Missing description. Explain what this value means and how to supply it.
params › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_create_customer",
"title": "Create Stripe Customer",
"description": "Create a customer in the client's Stripe account. The preview warns when Stripe already has a customer with that email. Nothing is created in the books. An email address set on a Stripe customer through NumbersGame is one Stripe will email invoices to, so a subscription for that customer is held (recipient_unconfirmed, nothing changed in Stripe) until a person confirms the address once in NumbersGame (Firm settings → Document sending → Recipients (or, for a firm without document sending, Firm settings → Stripe customer emails)) with a password or passkey; then call it again. No parameter skips this. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"name",
"realm_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 256,
"minLength": 1
},
"email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"description": {
"type": "string",
"maxLength": 500
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Create Stripe Customer",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Create a DRAFT invoice in the client's Stripe account. It is always a draft: NumbersGame never finalizes, sends or charges an invoice, so no money moves; a person reviews the draft and finalizes it in the Stripe Dashboard. Items are one-time Stripe prices (stripe_list_products) or an amount with a description; a recurring price goes on a subscription, created in the Stripe Dashboard (stripe_check_new_subscription checks it first). The preview flags prices with no revenue mapping and prices billed for more than a month (deferral). It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs64/100
7 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › price
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › quantity
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › amount
Without a price: the amount, major units.
Clear enough to supply this argument.
params › items › items › description
Without a price: what the line is for.
Clear enough to supply this argument.
params › collection_method
How Stripe collects once a person finalizes the draft in the Dashboard: charge the saved payment method, or email the invoice for payment.
Clear enough to supply this argument.
params › days_until_due
Payment terms in days; required when the invoice is emailed for payment rather than charged.
Clear enough to supply this argument.
params › description
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_create_invoice",
"title": "Create Stripe Invoice",
"description": "Create a DRAFT invoice in the client's Stripe account. It is always a draft: NumbersGame never finalizes, sends or charges an invoice, so no money moves; a person reviews the draft and finalizes it in the Stripe Dashboard. Items are one-time Stripe prices (stripe_list_products) or an amount with a description; a recurring price goes on a subscription, created in the Stripe Dashboard (stripe_check_new_subscription checks it first). The preview flags prices with no revenue mapping and prices billed for more than a month (deferral). It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"items",
"collection_method",
"realm_id"
],
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"price": {
"type": "string",
"pattern": "^price_[A-Za-z0-9]+$"
},
"amount": {
"type": "number",
"description": "Without a price: the amount, major units."
},
"quantity": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"description": {
"type": "string",
"description": "Without a price: what the line is for."
}
},
"additionalProperties": false
},
"maxItems": 100,
"minItems": 1
},
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"description": {
"type": "string",
"maxLength": 500
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"days_until_due": {
"type": "integer",
"maximum": 365,
"minimum": 0,
"description": "Payment terms in days; required when the invoice is emailed for payment rather than charged."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"collection_method": {
"enum": [
"charge_automatically",
"send_invoice"
],
"type": "string",
"description": "How Stripe collects once a person finalizes the draft in the Dashboard: charge the saved payment method, or email the invoice for payment."
}
}
}
}
},
"annotations": {
"title": "Create Stripe Invoice",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Check a subscription the client is about to set up in Stripe, before a person creates it: for the customer and prices, what Stripe would bill and when, what reaches the books (Stripe Receivables, revenue by product mapping, a deferral for multi-month billing), and what is wrong: prices with no ledger mapping, inactive or one-time prices, a currency that does not match the customer. Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
4 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › price
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › quantity
Not provided
Missing description. Explain what this value means and how to supply it.
params › days_until_due
Payment terms in days, when the invoices will be emailed for payment. Omit for a subscription that charges a saved payment method.
Clear enough to supply this argument.
params › coupon
Not provided
Missing description. Explain what this value means and how to supply it.
params › trial_end
Unix seconds the trial ends.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Check a New Stripe Subscription",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_check_new_subscription",
"title": "Check a New Stripe Subscription",
"description": "Check a subscription the client is about to set up in Stripe, before a person creates it: for the customer and prices, what Stripe would bill and when, what reaches the books (Stripe Receivables, revenue by product mapping, a deferral for multi-month billing), and what is wrong: prices with no ledger mapping, inactive or one-time prices, a currency that does not match the customer. Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"items",
"realm_id"
],
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "string",
"pattern": "^price_[A-Za-z0-9]+$"
},
"quantity": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"maxItems": 20,
"minItems": 1
},
"coupon": {
"type": "string"
},
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"trial_end": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Unix seconds the trial ends."
},
"days_until_due": {
"type": "integer",
"maximum": 365,
"minimum": 1,
"description": "Payment terms in days, when the invoices will be emailed for payment. Omit for a subscription that charges a saved payment method."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Check a New Stripe Subscription",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Check a change to a subscription's prices or quantities before a person makes it: `items` is the full new set (an existing price kept with its new quantity, others removed, new prices added). Returns Stripe's own preview of the next invoice, prorations included, and what the change does to the books (proration invoices and credit notes through the period summary, revenue on multi-month prices re-deferred). Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs46/100
3 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › price
Not provided
Missing description. Explain what this value means and how to supply it.
params › items › items › quantity
Not provided
Missing description. Explain what this value means and how to supply it.
params › proration_behavior
How Stripe would bill the change on the next invoice: prorate it (the default) or not at all.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_check_subscription_change",
"title": "Check a Stripe Subscription Change",
"description": "Check a change to a subscription's prices or quantities before a person makes it: `items` is the full new set (an existing price kept with its new quantity, others removed, new prices added). Returns Stripe's own preview of the next invoice, prorations included, and what the change does to the books (proration invoices and credit notes through the period summary, revenue on multi-month prices re-deferred). Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"items",
"realm_id"
],
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"required": [
"price"
],
"properties": {
"price": {
"type": "string",
"pattern": "^price_[A-Za-z0-9]+$"
},
"quantity": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"maxItems": 20,
"minItems": 1
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"proration_behavior": {
"enum": [
"create_prorations",
"none"
],
"type": "string",
"description": "How Stripe would bill the change on the next invoice: prorate it (the default) or not at all."
}
}
}
}
},
"annotations": {
"title": "Check a Stripe Subscription Change",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Cancel a subscription at the end of its current period (nothing more is billed after it), or NOW, optionally crediting unused time (prorate) to the customer's next invoice. Nothing is invoiced, charged or refunded from here; a refund is made in the Stripe Dashboard. Cancelling now cannot be undone in Stripe. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
3 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › when
Not provided
Missing description. Explain what this value means and how to supply it.
params › prorate
Not provided
Missing description. Explain what this value means and how to supply it.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_cancel_subscription",
"title": "Cancel Stripe Subscription",
"description": "Cancel a subscription at the end of its current period (nothing more is billed after it), or NOW, optionally crediting unused time (prorate) to the customer's next invoice. Nothing is invoiced, charged or refunded from here; a refund is made in the Stripe Dashboard. Cancelling now cannot be undone in Stripe. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"when",
"realm_id"
],
"properties": {
"when": {
"enum": [
"period_end",
"now"
],
"type": "string"
},
"prorate": {
"type": "boolean"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Cancel Stripe Subscription",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Issue a credit note on an open or paid Stripe invoice: whole lines (invoice_line, its full quantity or a quantity), part of a line (invoice_line with an amount), a custom line (description and amount), or one amount for the whole invoice. Called with only the invoice, the preview lists its lines and their il_ ids. Stripe takes it off what is still owed first; for the part on money already paid, paid_part_to says where it goes (customer_balance, outside_stripe), and the preview says when that is needed. It never refunds: a refund to the customer's card or bank is made in the Stripe Dashboard. The preview shows Stripe's own computation. NumbersGame does not email it. The next period summary books it: Dr Revenue and Sales tax / Cr Stripe Receivables. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs77/100
10 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › invoice
Not provided
Missing description. Explain what this value means and how to supply it.
params › lines › items › invoice_line
A line of the invoice (il_...), to credit it whole or in part.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
params › lines › items › quantity
For an invoice line: how many units to credit. Default: the whole line.
Clear enough to supply this argument.
params › lines › items › amount
Major units: part of an invoice line, or a custom line's amount.
Clear enough to supply this argument.
params › lines › items › description
A custom line: what the credit is for.
Clear enough to supply this argument.
params › amount
Instead of lines: one amount off the whole invoice, major units.
Clear enough to supply this argument.
params › reason
Not provided
Missing description. Explain what this value means and how to supply it.
params › memo
Printed on the credit note.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › paid_part_to
Where the part already paid goes: credit to the customer's balance, or repaid outside Stripe.
Clear enough to supply this argument.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_create_credit_note",
"title": "Issue Stripe Credit Note",
"description": "Issue a credit note on an open or paid Stripe invoice: whole lines (invoice_line, its full quantity or a quantity), part of a line (invoice_line with an amount), a custom line (description and amount), or one amount for the whole invoice. Called with only the invoice, the preview lists its lines and their il_ ids. Stripe takes it off what is still owed first; for the part on money already paid, paid_part_to says where it goes (customer_balance, outside_stripe), and the preview says when that is needed. It never refunds: a refund to the customer's card or bank is made in the Stripe Dashboard. The preview shows Stripe's own computation. NumbersGame does not email it. The next period summary books it: Dr Revenue and Sales tax / Cr Stripe Receivables. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"invoice",
"realm_id"
],
"properties": {
"memo": {
"type": "string",
"maxLength": 500,
"description": "Printed on the credit note."
},
"lines": {
"type": "array",
"items": {
"type": "object",
"properties": {
"amount": {
"type": "number",
"description": "Major units: part of an invoice line, or a custom line's amount.",
"exclusiveMinimum": 0
},
"quantity": {
"type": "integer",
"maximum": 9007199254740991,
"description": "For an invoice line: how many units to credit. Default: the whole line.",
"exclusiveMinimum": 0
},
"description": {
"type": "string",
"maxLength": 500,
"description": "A custom line: what the credit is for."
},
"invoice_line": {
"type": "string",
"pattern": "^il_[A-Za-z0-9_]+$",
"description": "A line of the invoice (il_...), to credit it whole or in part."
}
},
"additionalProperties": false
},
"maxItems": 50
},
"amount": {
"type": "number",
"description": "Instead of lines: one amount off the whole invoice, major units.",
"exclusiveMinimum": 0
},
"reason": {
"enum": [
"duplicate",
"fraudulent",
"order_change",
"product_unsatisfactory"
],
"type": "string"
},
"invoice": {
"type": "string",
"pattern": "^in_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"paid_part_to": {
"enum": [
"customer_balance",
"outside_stripe"
],
"type": "string",
"description": "Where the part already paid goes: credit to the customer's balance, or repaid outside Stripe."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Issue Stripe Credit Note",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Credit or debit a customer's Stripe balance; Stripe applies it to their next invoice(s). Nothing is charged or refunded now. The period summary does NOT book a balance adjustment, so the preview says what to book in the ledger (for a credit: Dr the concession account / Cr Stripe Customer credits). For a credit tied to an invoice, a credit note (stripe_create_credit_note) is usually right instead. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
6 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer
Not provided
Missing description. Explain what this value means and how to supply it.
params › direction
credit: the customer owes less; debit: they owe more.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › amount
Major units, in the customer's currency.
Clear enough to supply this argument.
params › description
Why; Stripe shows it on the customer's balance history.
Clear enough to supply this argument.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_adjust_customer_balance",
"title": "Adjust Stripe Customer Balance",
"description": "Credit or debit a customer's Stripe balance; Stripe applies it to their next invoice(s). Nothing is charged or refunded now. The period summary does NOT book a balance adjustment, so the preview says what to book in the ledger (for a credit: Dr the concession account / Cr Stripe Customer credits). For a credit tied to an invoice, a credit note (stripe_create_credit_note) is usually right instead. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"direction",
"amount",
"description",
"realm_id"
],
"properties": {
"amount": {
"type": "number",
"description": "Major units, in the customer's currency.",
"exclusiveMinimum": 0
},
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"direction": {
"enum": [
"credit",
"debit"
],
"type": "string",
"description": "credit: the customer owes less; debit: they owe more."
},
"description": {
"type": "string",
"maxLength": 350,
"minLength": 1,
"description": "Why; Stripe shows it on the customer's balance history."
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Adjust Stripe Customer Balance",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Pause collection on a subscription, optionally until a resume date, or remove a pause (action resume). While paused, behavior says what happens to each invoice: void (not billed; the usual choice), keep_as_draft (kept to send later) or mark_uncollectible (issued and written off, which books revenue and bad debt). The subscription stays active. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs64/100
5 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › action
Not provided
Missing description. Explain what this value means and how to supply it.
params › behavior
Required to pause.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › resumes_at
Pause only: the date billing resumes on its own, YYYY-MM-DD. Leave out to pause until resumed.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_pause_subscription",
"title": "Pause or Resume Stripe Subscription Billing",
"description": "Pause collection on a subscription, optionally until a resume date, or remove a pause (action resume). While paused, behavior says what happens to each invoice: void (not billed; the usual choice), keep_as_draft (kept to send later) or mark_uncollectible (issued and written off, which books revenue and bad debt). The subscription stays active. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"action",
"realm_id"
],
"properties": {
"action": {
"enum": [
"pause",
"resume"
],
"type": "string"
},
"behavior": {
"enum": [
"void",
"keep_as_draft",
"mark_uncollectible"
],
"type": "string",
"description": "Required to pause."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"resumes_at": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Pause only: the date billing resumes on its own, YYYY-MM-DD. Leave out to pause until resumed."
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Pause or Resume Stripe Subscription Billing",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
For a subscription managed by a schedule (a fixed term; Stripe refuses a cancel date on the subscription itself): set what happens when the term ends (end_behavior cancel, or release = it carries on and renews), or set or change a cancel date (cancel_on). A cancel date ends the schedule's last phase on that date and removes later phases; the preview lists them. A plain subscription is cancelled with stripe_cancel_subscription. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
4 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › end_behavior
Not provided
Missing description. Explain what this value means and how to supply it.
params › cancel_on
The date the subscription ends, YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_update_subscription_schedule",
"title": "Change Stripe Subscription Schedule End",
"description": "For a subscription managed by a schedule (a fixed term; Stripe refuses a cancel date on the subscription itself): set what happens when the term ends (end_behavior cancel, or release = it carries on and renews), or set or change a cancel date (cancel_on). A cancel date ends the schedule's last phase on that date and removes later phases; the preview lists them. A plain subscription is cancelled with stripe_cancel_subscription. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"realm_id"
],
"properties": {
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"cancel_on": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "The date the subscription ends, YYYY-MM-DD."
},
"end_behavior": {
"enum": [
"cancel",
"release"
],
"type": "string"
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Change Stripe Subscription Schedule End",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Put a discount on a subscription, or on one of its items (item: si_... or its price): an existing coupon, or a new_coupon made here, percent or amount off, once, for some months (repeating) or forever, optionally only on some products. Example: three free months on one add-on = percent_off 100, duration repeating, duration_in_months 3, products [the add-on's prod_]. Discounts already on it stay. Applies from the next invoice. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs63/100
8 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › coupon
An existing Stripe coupon id.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › new_coupon › name
Shown on the customer's invoices.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › new_coupon › percent_off
Not provided
Missing description. Explain what this value means and how to supply it.
params › new_coupon › amount_off
Major units, in the subscription's currency.
Clear enough to supply this argument.
params › new_coupon › duration
Not provided
Missing description. Explain what this value means and how to supply it.
params › new_coupon › duration_in_months
Not provided
Missing description. Explain what this value means and how to supply it.
params › new_coupon › products
Only these products are discounted.
Clear enough to supply this argument.
params › item
Discount one item only: its si_ id or its price_ id.
Clear enough to supply this argument.
params › confirm_token
Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview.
Clear enough to supply this argument.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_add_discount",
"title": "Add Discount to Stripe Subscription",
"description": "Put a discount on a subscription, or on one of its items (item: si_... or its price): an existing coupon, or a new_coupon made here, percent or amount off, once, for some months (repeating) or forever, optionally only on some products. Example: three free months on one add-on = percent_off 100, duration repeating, duration_in_months 3, products [the add-on's prod_]. Discounts already on it stay. Applies from the next invoice. It is TWO calls by design: the first, without confirm_token, changes nothing and returns what would change (in Stripe and in the books) plus a confirm_token; show that to the person, and only if they confirm, call again with the same arguments and the token. If Stripe changed in between, the second call returns the new preview instead of acting. Viewers and read-only companies cannot use it. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"realm_id"
],
"properties": {
"item": {
"type": "string",
"description": "Discount one item only: its si_ id or its price_ id."
},
"coupon": {
"type": "string",
"minLength": 1,
"description": "An existing Stripe coupon id."
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"new_coupon": {
"type": "object",
"required": [
"name",
"duration"
],
"properties": {
"name": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "Shown on the customer's invoices."
},
"duration": {
"enum": [
"once",
"repeating",
"forever"
],
"type": "string"
},
"products": {
"type": "array",
"items": {
"type": "string",
"pattern": "^prod_[A-Za-z0-9]+$"
},
"maxItems": 50,
"description": "Only these products are discounted."
},
"amount_off": {
"type": "number",
"description": "Major units, in the subscription's currency.",
"exclusiveMinimum": 0
},
"percent_off": {
"type": "number"
},
"duration_in_months": {
"type": "integer",
"maximum": 120,
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call: you get a preview and a confirm_token. Pass that token only after the person confirmed the preview."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Add Discount to Stripe Subscription",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Check an item the client is about to add to a subscription at a price made for it (unit_amount), on a product (product) or on an archived price's product (like_price), before a person adds it: it bills on the subscription's own currency and period from the next regular invoice, and the result shows Stripe's preview of that invoice, what reaches the books (revenue by the product's mapping), and what is wrong: a subscription that is not active, a product or price whose billing period differs from the subscription's. Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs47/100
4 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › subscription
Not provided
Missing description. Explain what this value means and how to supply it.
params › unit_amount
Price per unit per period, major units.
Clear enough to supply this argument.
params › product
Not provided
Missing description. Explain what this value means and how to supply it.
params › like_price
An archived price whose product this item is for.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › quantity
Not provided
Missing description. Explain what this value means and how to supply it.
params › proration_behavior
Not provided
Missing description. Explain what this value means and how to supply it.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Clear enough to supply this argument.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"title": "Check a New Stripe Subscription Item",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_check_subscription_item",
"title": "Check a New Stripe Subscription Item",
"description": "Check an item the client is about to add to a subscription at a price made for it (unit_amount), on a product (product) or on an archived price's product (like_price), before a person adds it: it bills on the subscription's own currency and period from the next regular invoice, and the result shows Stripe's preview of that invoice, what reaches the books (revenue by the product's mapping), and what is wrong: a subscription that is not active, a product or price whose billing period differs from the subscription's. Reads only: NumbersGame does not create or change subscriptions. The person makes the change in the Stripe Dashboard; afterwards, stripe_list_subscriptions with expected_deals confirms it was set up as agreed. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"subscription",
"unit_amount",
"realm_id"
],
"properties": {
"product": {
"type": "string",
"pattern": "^prod_[A-Za-z0-9]+$"
},
"quantity": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"like_price": {
"type": "string",
"pattern": "^price_[A-Za-z0-9]+$",
"description": "An archived price whose product this item is for."
},
"unit_amount": {
"type": "number",
"description": "Price per unit per period, major units.",
"exclusiveMinimum": 0
},
"subscription": {
"type": "string",
"pattern": "^sub_[A-Za-z0-9]+$"
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
},
"proration_behavior": {
"enum": [
"none",
"create_prorations"
],
"type": "string"
}
}
}
}
},
"annotations": {
"title": "Check a New Stripe Subscription Item",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
Align the title with the capability actually described by this tool.
Description89/100
Show a customer's saved Stripe payment methods and whether each can be charged automatically: for a US bank account (ACH), the authorization (mandate) and its status (active, pending verification, inactive); a card needs none. A bank account the customer entered but whose micro-deposits are not confirmed yet is listed too, as verification pending, with the date the deposits arrive and the customer's verification link: the authorization is started, so do not ask for a new one. Reads only: switching a subscription to automatic charging is done in the Stripe Dashboard. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.
The description explains the capability, when to use it, and what to expect.
Inputs58/100
2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
params › customer
Not provided
Missing description. Explain what this value means and how to supply it.
params › stripe_account
Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
params › realm_id
Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "stripe_payment_method_status",
"title": "Stripe Customer Payment Authorization",
"description": "Show a customer's saved Stripe payment methods and whether each can be charged automatically: for a US bank account (ACH), the authorization (mandate) and its status (active, pending verification, inactive); a card needs none. A bank account the customer entered but whose micro-deposits are not confirmed yet is listed too, as verification pending, with the date the deposits arrive and the customer's verification link: the authorization is started, so do not ask for a new one. Reads only: switching a subscription to automatic charging is done in the Stripe Dashboard. Stripe is the subledger: Stripe invoices, customers and payments are NOT ledger invoices, customers or payments, and are never created one-for-one in QuickBooks or Xero. The ledger gets period totals through Stripe Receivables and Stripe Clearing.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"params"
],
"properties": {
"params": {
"type": "object",
"required": [
"customer",
"realm_id"
],
"properties": {
"customer": {
"type": "string",
"pattern": "^cus_[A-Za-z0-9]+$"
},
"realm_id": {
"type": "string",
"description": "Which company to act on: the id from the project's company file, from list_companies on the main NumbersGame connector, or from the user (it is on the company's page in the portal). Digits for QuickBooks, a GUID for Xero. Never guess one or reuse an example; if you do not have it, ask the user."
},
"stripe_account": {
"type": "string",
"pattern": "^acct_[A-Za-z0-9]+$",
"description": "Which connected Stripe account (acct_...). Needed only when more than one is connected to this company; stripe_status lists them."
}
}
}
}
},
"annotations": {
"title": "Stripe Customer Payment Authorization",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}
Loading score analytics…
Put your MCP to the test
A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.
01List CompaniesList the companies you can use through this connection (a connection can be limited to chosen companies; connection_covers says which): each one's name, real…
02Profit and LossPull Profit and Loss (Income Statement) data from QuickBooks Online or Xero.
03Cash Flow StatementPull the Statement of Cash Flows from QBO.
04Get InvoiceRead a single customer invoice from QuickBooks Online or Xero by its ID.
05General LedgerPull the General Ledger Detail report from QBO.
Want to run these tasks against your MCP server with us?
QuickBooks Online MCP Server setup, tools, quality score, publishing readiness, and alternatives.
How do I add QuickBooks Online MCP Server to Claude, ChatGPT, or Cursor?
Add QuickBooks Online MCP Server to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.numbersgame.xyz/mcp.
Is QuickBooks Online MCP Server MCP ready for ChatGPT and Claude?
As of November 16, 2026, QuickBooks Online MCP Server scores 96/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is QuickBooks Online MCP Server's MCP tool documentation?
As of November 16, 2026, QuickBooks Online MCP Server scores 76/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 265 of 265 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to QuickBooks Online MCP Server?
As of November 17, 2026, alternatives to QuickBooks Online MCP Server in financial-services on the Manufact MCP leaderboard include Blockworks, SHVL credit control, BankConv, Economico, and DefiLlama.
How can QuickBooks Online MCP Server improve its MCP documentation?
update_journal_entry is the lowest-scoring reviewed tool at 58/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.