Skip to main content
Glama
Sign In

opentax

by io.github.Invaro
OverviewDiscussionsAdmin

lookup_tax_parameter

Look up the current-law dollar amounts behind a question ('standard deduction', 'CTC phase-out threshold', 'tips deduction cap') with their statutory citations and validity windows. Use this to fact-check ANY tax number before stating it — your training data likely predates the OBBBA.

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": {
      "query": "<query>"
    },
    "name": "lookup_tax_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
queryYesplain-English search, e.g. 'standard deduction'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / maxLength
      Added value: +2000
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that the tool returns current-law dollar amounts with statutory citations and validity windows, and implies a read-only lookup rather than a calculation or mutation. It does not explicitly state side-effect safety, authentication needs, rate limits, or behavior on unknown queries, so it is strong but not fully transparent.

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

Conciseness5/5

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

The description is two tightly written sentences with zero waste. The core purpose and examples are front-loaded, followed by a concise usage directive, making it easy for an agent to parse quickly.

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 has no output schema and no annotations, so the description usefully states that results include dollar amounts, citations, and validity windows. It remains slightly incomplete because it does not explain how 'asOf' affects results or what happens when a query is ambiguous or unmatched, but the overall context is sufficient for a simple lookup tool.

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 coverage is 50%: the 'query' parameter already has a plain-English search description, while 'asOf' has only a date pattern and no description. The description adds useful query examples and mentions validity windows, which hints at temporal lookup, but it does not explain the 'asOf' parameter's meaning or behavior, leaving a meaningful gap.

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

Purpose5/5

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

The description uses a specific verb and resource: looking up current-law dollar amounts behind a tax question. It gives concrete examples ('standard deduction', 'CTC phase-out threshold', 'tips deduction cap') and states that results include statutory citations and validity windows, which clearly distinguishes it from sibling tools that calculate, explain, or verify rules.

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

Usage Guidelines4/5

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

The description gives clear usage guidance: use it to fact-check ANY tax number before stating it, and warns that training data may predate the OBBBA. It does not explicitly name alternative sibling tools or when not to use this one, but the intended context is strong and specific.

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

All opentax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources