Skip to main content
Glama

taxme_results

Retrieves the calculated tax amount from the open tax return in the TaxMe portal. Confirms the results section is open, then reads the figure from the page.

Instructions

Read the Ergebnisse / Steuerberechnung of the open return. Reaching that section is a precondition, and it is settled the way taxme_goto_section settles it — by the menu entry the breadcrumb names — before a word of the page is read: a portal that refused to open the section comes back as an error naming the page you are really on instead of that page's text. A breadcrumb that names no entry of this menu settles nothing there, though, and where it has settled nothing the page itself has to say the section is open before an amount is read off it: the calculation is only ever read from a line the word HEADS — never from the left-menu entry, which is on every page of the return — and, absent a breadcrumb naming the entry, only when that line IS a heading of the page (a heading tag, a legend, a caption, a title/header panel) rather than a sentence beginning with the same word, since a refusal banner can be written either way round and word order is the portal's phrasing, not evidence about which page is open. A click that landed on a page with no menu at all — an expired session lands on the login form — is reported as no return being open, not as a page carrying no calculation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries the full burden. It reveals several key behaviors: the requirement to have the section open via breadcrumb, the error behavior when the portal refuses (returns the actual page name), the rule that the calculation is only read from a line containing HEADS and only when that line is a heading element, and the handling of expired sessions (reports no return open). This is rich behavioral disclosure.

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

Conciseness2/5

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

The description is a single dense paragraph with many nested clauses. While the first sentence is clear, the rest is a long, convoluted explanation of edge cases that could be broken up or summarized. It is not concise or easily scannable.

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 description covers the main purpose, preconditions, error cases, and the specific rule for identifying the calculation line. However, it does not explicitly describe the return value format beyond implying it reads an amount. Given the absence of an output schema, this is a minor gap, but overall the tool is well-contextualized.

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

Parameters4/5

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

The tool has zero parameters, so there is nothing to document beyond the schema. The baseline for 0-param tools is 4, and the description doesn't need to add parameter details.

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 a clear statement: 'Read the Ergebnisse / Steuerberechnung of the open return.' This specifies the verb (read), the resource (Ergebnisse/Steuerberechnung), and the scope (open return). It distinguishes from sibling tools like taxme_get_fields and taxme_snapshot by focusing on the calculation section.

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?

The description implies the tool is for reading the tax calculation once the section is open, but it does not explicitly state when to use it versus alternatives. It mentions preconditions (reaching the section) but does not name any alternative tools or exclusion criteria. Thus, usage is implied rather than explicitly guided.

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