Skip to main content
Glama

taxme_goto_section

Navigate to a named section of an open tax return and retrieve its fields. Reports errors if navigation fails due to form issues or an expired session.

Instructions

Click a menu section by name (substring) in the open return; returns the fields on that page, cut at 60 like taxme_get_fields and saying so with truncated/total. Landing there is checked: TaxMe refuses to open a section while the form still has errors, and the page it hands back instead comes back as an error naming the section you are really on — not as that section's fields under the name you asked for. Which section that is is decided by the menu entry the breadcrumb names, not by the name appearing somewhere in it, because these names nest both ways round ("Wertschriften" at the front of "Wertschriftenverzeichnis", "Einkünfte" at the end of "Übrige Einkünfte"). A breadcrumb is a path and the page is the end of it, so it is read as a path: the last of its steps that names an entry of this menu, and within that step the longest entry, since a longer name that fits contains every shorter one nested inside it. A page carrying no menu is no return at all — an expired session lands on the login form — and comes back as an error saying so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
Behavior5/5

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

Without annotations, the description carries full responsibility for behavioral disclosure, and it excels. It details substring resolution via breadcrumb paths, error handling for form validation and expired sessions, and the truncation behavior ('cut at 60... with truncated/total'). This goes far beyond a basic operation description.

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 dense and lengthy, but it is front-loaded with the core action in the first sentence. Every subsequent sentence adds necessary nuance for a complex matching algorithm and error scenarios. It is appropriately sized for the complexity, though not as crisp as a simpler tool's description.

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 single parameter, no annotations, and no output schema, the description covers all essential aspects: operation, output format (fields with truncation), error conditions (form errors, expired session), and resolution logic. It also references taxme_get_fields to clarify output behavior, making it effectively complete for an agent.

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 only parameter 'name' receives extensive semantic explanation: it is a substring that must match a menu entry as determined by breadcrumb resolution, with examples ('Wertschriften' at front, 'Einkünfte' at end). This adds tremendous meaning beyond the bare schema string type, especially given 0% schema description coverage.

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 clearly states the tool's primary function: 'Click a menu section by name (substring) in the open return; returns the fields on that page.' This specific verb+resource combination distinguishes it from siblings like taxme_menu (which lists sections) and taxme_get_fields (which fetches fields without navigation).

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 implies usage context by specifying 'in the open return' and notes a critical precondition: 'TaxMe refuses to open a section while the form still has errors.' It does not explicitly name alternative tools or when-not-to-use scenarios, but the context is clear enough for an agent to select this tool for section navigation.

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