Skip to main content
Glama
Sign In

presupuestos.red

by io.github.joseanu
OverviewDiscussionsAdmin

Abrir presupuesto

abrir_presupuesto
Read-onlyIdempotent

Llama sin argumentos para abrir el selector de archivos. Para reabrir una revisión publicada, indica presupuestoId y version juntos. El visor permite buscar conceptos, consultar sus APU y abrir una fuente con sourceId. Para un documento privado, usa la cuenta propietaria o el enlace de lectura vigente.

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

Input Schema

NameRequiredDescriptionDefault
versionNoNúmero de la revisión publicada que quieres consultar. Usa el que acompaña al presupuesto en el contexto del visor.
sourceIdNoReferencia de la evidencia que quieres ver en el visor. Copia el valor exacto que devolvió la consulta del concepto, renglón, recurso o cálculo.
presupuestoIdNoIdentifica 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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds real value by disclosing access constraints: private documents require the owner account or a currently valid read link. It does not describe the UI outcome or what happens when a version is stale, but that is a minor gap given the annotation coverage and the output schema.

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-loads the no-argument call, then the reopen case, then the private-document workaround, which matches the order an agent would need. The sentence enumerating viewer capabilities is somewhat tangential to invoking this tool and could be trimmed.

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?

With an output schema, full schema coverage, and annotations carrying the safety profile, the description only needs to cover invocation modes and access rules, which it does. The one omission is any hint about what to do if the given version or share link is invalid.

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 five parameters are already documented. The description adds one genuinely new constraint, that presupuestoId and version must be supplied together, and frames sourceId as opening an evidence source, but readSharePath and conversation_id receive no added meaning beyond their schema text. Baseline 3 is appropriate.

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?

States a specific verb and resource ("abrir el selector de archivos", "reabrir una revisión publicada") and distinguishes two operating modes of the same tool. It also names viewer capabilities (buscar conceptos, consultar APU) that belong to sibling tools, which slightly blurs the boundary of what this tool itself does.

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?

Gives explicit invocation conditions: no arguments to open the file selector, presupuestoId plus version together to reopen a published revision, and owner account or a valid read link for private documents. It does not explicitly exclude or redirect to a named sibling, but the mode selection is clear enough to act on.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All presupuestos.red toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources