Skip to main content
Glama

Annual income tax summary (self-employed)

get_income_tax_summary
Read-onlyIdempotent

Annual summary of the self-employed activity for the Spanish income tax return (IRPF, direct estimation): income and deductible expenses grouped by tax-return box, totals and net result, only what has already accrued. Includes documents whose accrual date is unconfirmed. Needs the self-employed module.

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_income_tax_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
yearNoTax year (default: current year).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: the module prerequisite, the accrual-only scope, and the notable inclusion of documents whose accrual date is unconfirmed — a data-quality caveat an agent would otherwise not know.

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?

Two dense sentences that lead with the resource and scope before the caveats. Slight redundancy between the parenthetical "IRPF, direct estimation" and the title, but every clause carries information.

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?

With no output schema, the description takes on the burden of describing return content, and it does: income and deductible expenses grouped by tax-return box, plus totals and net result. The prerequisite and the unconfirmed-accrual inclusion are also stated, leaving only minor gaps such as whether the result is a document or an inline object.

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 100%, so both parameters (book id sourced from list_books, year with a 2000-2100 range and current-year default) are fully documented in the schema. The description adds no further parameter meaning, which is the expected baseline when the schema does the work.

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?

States a specific verb+resource (annual summary of self-employed activity) and pins it to a domain: Spanish IRPF direct estimation, income and deductible expenses grouped by tax-return box with totals and net result. The word "annual" plus the tax-box framing distinguishes it from the monthly sibling and from document-listing tools without needing to name them.

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?

Gives an explicit prerequisite ("Needs the self-employed module") and an implicit scoping rule ("only what has already accrued" excludes forward-looking data such as get_forecast), but never routes the agent between this tool and get_month_summary or get_tax_periods. The when-to-use is inferable from the name rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources