Skip to main content
Glama
Sign In
ArcaTax

ArcaTax

by Accuarion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_return_status

Summarizes the tax return data currently on file and lists open gap-analysis questions for a given tax year.

Instructions

Summarize what is on file for the return and list the open gap-analysis questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_return_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read operation via "summarize" and "list" but says nothing about permissions, scope (federal only vs. state), pagination, or how the gap questions are derived. Output schema exists, which relieves the return-value burden, but the operational profile is thin.

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?

A single compact sentence with no filler, front-loading the primary action (summarize current state) before the secondary output (gap questions). Nothing is wasted, though the phrasing "what is on file for the return" is mildly vague.

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

Completeness3/5

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

The tool is simple, has an output schema documenting return values, and only one optional parameter, so the description covers the core. However, with zero annotation coverage and an undocumented tax_year, an agent still lacks enough to call it confidently in edge cases.

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

Parameters2/5

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

There is one parameter, tax_year, with a default of 2026 and 0% schema description coverage, and the description never mentions it. It is unclear whether tax_year scopes the whole summary or only part of it, or what happens when it is omitted.

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?

The description pairs specific verbs ("summarize", "list") with concrete resources ("what is on file for the return", "open gap-analysis questions"), so an agent can tell this is a read-only status/aggregation tool. It is implicitly distinct from the upsert_* and calculate_* siblings, but never states that contrast explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as calculate_1040_return. At best the phrase "what is on file" implies a pre-check of current state, which the agent must infer.

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

Deploy Server

Other Tools