Skip to main content
Glama
Sign In

presupuestos.red

by io.github.joseanu
OverviewDiscussionsAdmin

Busca conceptos

buscar_conceptos
Read-onlyIdempotent

Busca conceptos por código, descripción y partida; devuelve hasta 10 candidatos y nextCursor para continuar. Puede acotar a partidaId; con partidaId permite query vacío para recorrer sus conceptos en orden del presupuesto. 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>"
    },
    "name": "buscar_conceptos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCódigo o texto del concepto o partida que buscas. Con partidaId puedes recorrer la partida sin texto de búsqueda.
cursorNoPosición desde la que se retoma la lectura. Usa nextCursor de la página anterior.
versionYesNúmero de la revisión publicada que quieres consultar. Usa el que acompaña al presupuesto en el contexto del visor.
partidaIdNoID de partida devuelto en mapaPartidas.partidas por obtener_resumen_presupuesto o como wbsNodeId en la tabla presupuesto.
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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's 'No guarda cambios' largely restates that. It does add genuine behavioral context beyond annotations — the 10-candidate page cap with nextCursor, and the access model (owner account, public document, or valid read link via readSharePath) — but says nothing about ordering of results for text queries or error/empty-result behavior.

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-loaded with the verb, resource, and pagination limit, followed by scoping, context, and access notes — a logical order with no filler. The closing 'No guarda cambios ni emite una opinión profesional' is partly redundant with readOnlyHint, though the professional-opinion disclaimer carries some independent value.

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 structure need not be spelled out, and the description still adds the page size and nextCursor contract plus the access prerequisites, which are the main behavioral risks for a search tool. Adequate for a read-only search; only result ordering for text queries and the behavior when no candidates match are left implicit.

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 the schema already documents query, partidaId, cursor, version, presupuestoId and readSharePath thoroughly. The description only restates the partidaId-plus-empty-query combination and the cursor continuation, adding no new syntax, format, or defaulting information beyond the schema.

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 ('Busca conceptos') plus the searchable fields (código, descripción, partida) and the result shape (up to 10 candidates + nextCursor). It is clearly distinguishable in practice from siblings like obtener_resumen_presupuesto or consultar_apu, but it never names an alternative tool to redirect the agent, so it stops short of full sibling differentiation.

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 real usage context: scope can be narrowed with partidaId, and with partidaId an empty query is allowed to walk a partida in budget order, plus the instruction to rely on the open-budget context. It lacks explicit 'when not to use this' guidance or a named alternative for concept lookup by other means.

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