Skip to main content
Glama

presupuestos.red

Señales deterministas del presupuesto

consultar_diagnostico_presupuesto
Read-onlyIdempotent

Devuelve las señales del motor de Análisis antes de la selección ejecutiva de la UI. Sirven para orientar investigación, no son errores probados ni hallazgos del agente. El motor limita la selección y las entidades relacionadas son ejemplos. 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": "consultar_diagnostico_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

B3.3/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses two substantive behaviors: results are intentionally capped ('el motor limita la selección') with related entities as illustrative examples, and access is gated by owner account, public status, or a valid read link. It also confirms no changes are persisted and no professional opinion is issued. Only the output format specifics are left unaddressed, which the output schema covers.

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

Conciseness3/5

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

Sentences are short and each carries some content, and the caveats about non-findings and access come reasonably early. But the opening 'antes de la selección ejecutiva de la UI' is opaque filler that delays the actual purpose, and the sequence of short declaratives reads as a list of disclaimers rather than a front-loaded explanation.

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?

For a read-only diagnostic tool with an output schema and six documented parameters, the description covers the essential unknowns: what the signals are not, that selection is limited, that related entities are examples, and what grants access. The remaining gap is relational — how these signals differ from data returned by sibling consultation tools.

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 every parameter is already documented, and the description adds only the general instruction to take values from the open budget context. That lightly reinforces presupuestoId, version, and readSharePath without adding new syntax or constraints. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns 'las señales del motor de Análisis' that guide investigation and are not proven errors, which conveys the diagnostic character of the output. However, 'señales' is never concretely defined, and the phrase 'antes de la selección ejecutiva de la UI' adds no discriminative meaning. Nothing distinguishes it from siblings like consultar_datos_presupuesto or obtener_resumen_presupuesto.

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?

It gives an implied context of use — 'sirven para orientar investigación' — and says to use the context of the open budget, which sets a precondition. But it never states when to prefer this over another consultation tool, nor any explicit exclusion beyond the caveat that the signals are not proven findings.

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