Skip to main content
Glama

taxme_submit_return

Submit your finalized tax return in TaxMe. Requires confirmation and only proceeds when the official Abschluss page is open, preventing accidental or invalid submissions.

Instructions

DANGER: final submission (Abschluss → Steuererklärung einreichen). Irreversible. Requires confirm:true; otherwise returns a dry-run of the Abschluss page, naming in would_click the one button a confirmed call would press. Reaching that page is a precondition: if no submit button is there, the call is refused rather than pressing whatever the current page happens to offer. A page that already reports the return as filed (already_submitted) is refused too, confirm:true and all — a confirmation that was on the page beforehand could not prove anything about a second click. A page whose text could not be read at all (page_unreadable) is refused for the same reason one step further back: a read that failed is not a page that said no. In both cases the submit button is named as not_clicked rather than would_click, because nothing would be pressed. And a page carrying no menu at all is no return — an expired session lands on the login form — which is said in those words rather than as the Abschluss page merely not being open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
Behavior5/5

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

With no annotations, the description carries full burden and does so impressively. It discloses irreversibility, dry-run behavior when confirm is false, the would_click/not_clicked distinction, and every refusal case including expired sessions. This goes far beyond basic operation and fully informs the agent of all safety behaviors.

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?

The description is a single verbose paragraph, but every sentence communicates a distinct edge case or behavioral rule, earning its place. It is longer than ideal, but the high stakes justify thoroughness. Minor deduction for lack of structural formatting like bullet points.

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

Completeness5/5

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

Given the complexity of an irreversible submission, no annotations, and no output schema, the description is exceptionally complete. It covers preconditions, response outcomes (dry-run vs actual click), and all refusal scenarios, leaving the agent well-equipped to invoke it correctly.

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

Parameters5/5

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

The schema only defines a boolean 'confirm' with no description. The description explains that confirm:true is required for actual submission, and false triggers a dry-run, adding meaning that is absent from the schema. Since schema coverage is 0%, this is essential and well-handled.

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 opens with 'DANGER: final submission' and 'Abschluss → Steuererklärung einreichen', clearly indicating this tool performs the final tax return submission. It is distinctly different from sibling tools by emphasizing irreversibility and the submit button, leaving no ambiguity about what action it performs.

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 explicit preconditions: the user must be on the Abschluss page and confirm must be true. It also details when the tool refuses to act (already submitted, page unreadable, no menu). However, it does not explicitly name alternative sibling tools for other contexts, so it lacks direct comparative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sapn95/taxme-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server