Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Form 1099 threshold check

accounting-schedules_form-1099-threshold-check
Read-onlyIdempotent

Sum payee payments by category for tax year 2026 and flag 1099-NEC / 1099-MISC boxes that meet IRS thresholds. Price $0.02 USDC. POST /api/v1/accounting-schedules/form-1099-threshold-check. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taxYear": "<taxYear>",
      "payments": "<payments>"
    },
    "name": "accounting-schedules_form-1099-threshold-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearYestaxYear, integer, from -9007199254740991 to 9007199254740991. Required.
paymentsYespayments, array. Required.

Output Schema

NameRequiredDescriptionDefault
payeesNopayees. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description usefully adds what annotations cannot: a $0.02 USDC price, the exact POST path, and the non-obvious fact that an unpaid call returns x402 payment terms instead of running the computation. That payment-gating behavior is exactly the kind of context an agent needs before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the computation and outcome before cost and transport details. Nothing is padded. The raw endpoint path is marginal value for an agent that already has the tool registered, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 required parameters), an output schema exists to explain return values, and annotations cover the safety profile. The description adds the one thing structured fields do not carry: the paid-call mechanic. Its only real gap is the 2026-versus-taxYear tension and silent treatment of card payments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the two parameters are already documented and the baseline is 3. The description adds little beyond that, and in fact hardcodes 'tax year 2026' while the schema accepts any integer taxYear, which could mislead an agent into assuming the year is fixed. It also says nothing about how paidByCardOrThirdParty or the category enum affect which 1099 box is flagged.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource: sum payee payments by category and flag 1099-NEC / 1099-MISC boxes against IRS thresholds. An agent can tell this apart from the schedule-building siblings (depreciation, lease, revenue recognition) by the tax-reporting outcome alone. It stops short of naming an alternative, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it needs 1099 box determination for a payee set. There is no statement of when not to use it or which sibling handles adjacent work (e.g. journal or trial-balance tasks). The payment prerequisite is covered, but selection guidance is not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources