Skip to main content
Glama

Quarterly tax returns (self-employed)

get_tax_periods
Read-onlyIdempotent

Self-employed periodic tax returns of a year as computed by Cuéntamo for the account book's tax regime (Spain: VAT form 303 and income-tax instalment form 130, or the regional/IGIC equivalents): amounts per period, payment calendar with due dates, and warnings. The figures already apply the regime's rules (accrual dates, deductibility, periods marked as filed). 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_tax_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
yearNoDefault: current year.
periodNoQuarter (1-4) or month, depending on the regime. Omit for the whole year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low; the description still adds real substance by explaining that figures pre-apply regime rules (accrual dates, deductibility, filed-period marking) and that warnings accompany the data. This tells the agent the output is pre-processed rather than raw transactions, and flags the module prerequisite.

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?

Front-loads the core purpose and what is returned, then adds regime/calculation context and the prerequisite. It is dense with a long parenthetical listing of forms, but each clause carries information an agent needs; no filler sentences.

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 must characterize the return payload, and it does so concretely (per-period amounts, payment calendar with due dates, warnings). Combined with the stated module prerequisite and 100% schema coverage on inputs, only the regime-specific edge cases and error behavior when the module is absent remain unstated.

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 description coverage is 100%, so book, year, and period are already documented, including defaults and the 1-12 quarter-or-month ambiguity. The description only reinforces that the result is scoped to 'a year' and is regime-dependent; it adds little syntactic or semantic detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: periodic self-employed tax returns computed by Cuéntamo, enumerating the concrete artifacts returned (amounts per period, payment calendar with due dates, warnings) and the relevant Spanish forms 303/130 or IGIC equivalents. The scope is unambiguous against a generic tax summary, though it does not explicitly name the sibling it differs from (e.g. get_income_tax_summary).

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?

Provides one real usage constraint — 'Needs the self-employed module' — which tells the agent a precondition and likely failure mode. However, there is no explicit when-to-use vs when-not guidance and no routing to siblings such as get_income_tax_summary or list_tax_documents, so the alternative selection is only implied.

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