Skip to main content
Glama

Ver cómo van mis impuestos

gestoria_get_tax_status
Read-onlyIdempotent

Use this when a connected Kuotia gestoría client asks how their taxes are going: which periods are being prepared, ready to file or filed, deadlines, and the amounts their gestor has made ready or filed. Amounts appear only for ready or filed returns. Read only: it never files, approves or changes anything. Do not use for general deadlines or estimates (public tools).

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": "gestoria_get_tax_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoOne period (2026-T3, 2026-07 or 2026). Without it: the open periods and the last four filed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral detail beyond them: it never files or approves, and amounts surface only for ready or filed returns, which tells the agent why some periods show no numbers. It stops short of describing ordering or return shape, though the output schema covers that.

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-loaded with the use case, then the return contents, then the read-only guarantee, then the exclusion — a sensible priority order with no filler. The first sentence is long and list-heavy, but every clause carries information an agent needs.

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?

For a single-optional-param read tool with full annotations and an output schema, the description covers the remaining gaps: client eligibility, what amounts are visible, and the read-only guarantee. Nothing required to call it correctly is missing.

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?

The single optional `period` parameter has 100% schema coverage including the accepted formats and the default behavior when omitted, so the description adds nothing about parameters. Baseline 3 applies when the schema carries the full burden.

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 names a specific verb+resource (retrieve tax status for a connected Kuotia gestoría client) and enumerates the exact payload: periods in preparation, ready to file, filed, deadlines, and amounts. It also explicitly separates itself from the public deadline/estimate tools, so an agent can route without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition ('when a connected Kuotia gestoría client asks how their taxes are going') and an explicit exclusion ('Do not use for general deadlines or estimates (public tools)'), covering both when and when-not in one place.

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