Skip to main content
Glama

Ver lo que me pide mi gestor

gestoria_list_requests
Read-onlyIdempotent

Use this when a connected gestoría client asks what their gestor needs from them or whether something they sent arrived. Lists each pending or sent request with its type, period, due date and a portal link; the client answers in the Kuotia portal. Do not use to answer or create requests.

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

Input Schema

NameRequiredDescriptionDefault
statusNopending

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful operational context: answers happen in the Kuotia portal, not through this tool, so calling it cannot resolve a request. It does not mention ordering, pagination, or what happens with no connected gestoría, so it only marginally exceeds the annotation baseline.

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 sentences, front-loaded with the trigger, then the content, then the exclusion. No redundant restatement of name or annotations, and 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?

An output schema exists, so return-value detail needn't be spelled out, and annotations cover safety. The definition is complete enough to call correctly, with only minor gaps: the status default and the meaning of 'sent' are unstated, and there's no note on what an empty list means for an unconnected client.

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 schema has 0% description coverage for its one parameter, but the enum values (pending/sent/all) are self-explanatory and the description's phrase 'pending or sent request' implicitly maps to them. It doesn't state the default ('pending') or clarify whether 'sent' means requests sent to the client or responses sent by the client — a real ambiguity given the 'did something they sent arrive' framing.

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 and resource ('Lists each pending or sent request') plus the fields returned (type, period, due date, portal link) and the user situation that triggers it. It is distinguishable from siblings like gestoria_get_obligations and gestoria_send_message because it is framed around requests the gestor has made of the client.

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?

Gives an explicit when-to-use trigger ('when a connected gestoría client asks what their gestor needs from them or whether something they sent arrived') and an explicit exclusion ('Do not use to answer or create requests'). The client-facing framing makes clear this is not the tool for obligations or tax status lookups.

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