Skip to main content
Glama

presupuestos.red

Resumen del presupuesto

obtener_resumen_presupuesto
Read-onlyIdempotent

Obtiene el resumen económico y un mapa de partidas. Los importes por partida incluyen sus descendientes y se expresan en la base declarada; la cobertura de matrices no certifica una revisión completa. Usa el contexto del presupuesto abierto. El acceso depende de la cuenta propietaria, de que el documento sea público o del enlace de lectura vigente. No guarda cambios ni emite una opinión profesional.

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": {
      "presupuestoId": "<presupuestoId>",
      "version": "<version>",
      "context": "<context>"
    },
    "name": "obtener_resumen_presupuesto"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
versionYesNúmero de la revisión publicada que quieres consultar. Usa el que acompaña al presupuesto en el contexto del visor.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
presupuestoIdYesIdentifica el documento. Tómalo del contexto que devuelve el visor al importar o abrir el presupuesto.
readSharePathNoEnlace que da acceso de lectura a un presupuesto compartido. Para un documento privado compartido, toma este valor del contexto con el que lo abriste.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "presupuestoId",
      -  "version"
      -]New value: +[
      +  "presupuestoId",
      +  "version",
      +  "context"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: amounts aggregate descendant line items, are expressed in the declared basis, matrix coverage does not certify a complete review, and access depends on ownership/public status/read link. The disclaimer that it 'no emite una opinión profesional' is a useful scope limit, though 'No guarda cambios' partly restates readOnlyHint.

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?

The purpose is front-loaded in the first sentence, followed by data-semantics caveats, access rules, and scope disclaimers. Every sentence carries information, with no filler. Some phrasing ('la cobertura de matrices no certifica una revisión completa') is terse to the point of being cryptic, slightly taxing readability.

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?

An output schema exists, so return values need not be described, and all parameters are fully documented in the schema. The description still covers the things structured fields cannot: authorization model, aggregation semantics, and interpretive caveats. For a read-only summary tool, this leaves no material gap for correct invocation.

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 all six parameters are documented in the schema itself, and the description only echoes that the open-budget context supplies the identifiers. No additional syntax, format, or meaning is added for version, presupuestoId, readSharePath, or the analytics fields. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Obtiene el resumen económico y un mapa de partidas', which clearly identifies an economic summary plus a line-item map. It does not, however, name or contrast itself with close siblings like consultar_datos_presupuesto or consultar_diagnostico_presupuesto, so the agent must infer the boundary. Purpose is clear but sibling differentiation is absent.

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?

The line 'Usa el contexto del presupuesto abierto' implies the tool is called against an already-open budget, giving an implicit usage condition. Access prerequisites (owner account, public document, or current read link) are spelled out, which helps. But there is no explicit when-to-use vs when-not, and no alternative tool is named.

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