Skip to main content
Glama

Ver mis obligaciones del año

gestoria_get_obligations
Read-onlyIdempotent

Use this when a connected gestoría client asks which returns they must file in a year and by when, as their gestor confirmed them. Do not use for someone who is not a connected client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "gestoria_get_obligations"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds two useful pieces of behavioral context beyond that: the data is gestor-confirmed and the call only applies to connected clients. However it says nothing about what happens for an unconnected client or an out-of-range year, so the added context is real but modest.

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

Conciseness5/5

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

Two tight sentences: the usage condition is front-loaded, followed immediately by the exclusion. Nothing is redundant and no sentence could be dropped without losing decision-relevant 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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. For a single-parameter read tool the description covers who, why, and when-not adequately; only the acceptable year range and unconnected-client behavior are left to structured fields.

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?

With one parameter and 0% schema description coverage, the description must supply meaning, and it does partly by framing the year as the fiscal year of the filing obligations. It adds no format or boundary context (the allowed 2025-2027 window appears only in the schema), so it compensates only at a baseline level.

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?

The description names a concrete resource and scope: returns a connected gestoría client must file within a year, plus their deadlines, and qualifies the source as 'as their gestor confirmed them'. It does not explicitly differentiate from siblings like gestoria_get_tax_status, but the 'obligations to file + deadlines' framing is specific enough to separate it from a generic status lookup.

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?

It gives an explicit when-to-use condition (a connected gestoría client asking which returns they must file and by when) and an explicit exclusion ('Do not use for someone who is not a connected client'). The only gap is that it does not name a sibling to redirect non-client or status-only questions to.

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