presupuestos.red

Iniciar importación

iniciar_importacion

Crea un intento persistente para el archivo seleccionado en la interfaz. Con cuenta verificada asigna propietario; sin cuenta crea un invitado. No repetir automáticamente si se pierde la respuesta.

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": {
      "filename": "<filename>",
      "size": "<size>",
      "requireAccount": "<requireAccount>"
    },
    "name": "iniciar_importacion"
  }
}

Input Schema

Name	Required	Description
`size`	Yes	Tamaño del archivo en bytes.
`filename`	Yes	Nombre del archivo seleccionado.
`requireAccount`	Yes	Impide cambiar a invitado un intento iniciado con cuenta.
`conversation_id`	No	The 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, and the description reinforces the latter with a concrete operational warning about lost responses. It also discloses the branching behavior (verified account assigns an owner, otherwise a guest is created) and that the attempt is persisted, which is context annotations cannot carry.

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?

Three short sentences, each carrying distinct information: what is created, how ownership branches, and the retry prohibition. The most important constraint is placed last for emphasis with zero filler.

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 values need not be explained, and the description covers persistence, ownership branching, and the non-idempotency hazard. The main remaining gap is what failure looks like and whether a failed attempt can be resumed rather than recreated.

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 baseline is 3. The description loosely explains the account-versus-guest outcome that requireAccount controls, but adds no detail on filename, size limits, or the analytics-only conversation_id parameter.

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 concrete verb and resource: creates a persistent attempt for the selected file. It is distinguishable from the budgeting siblings, none of which deal with uploads or attempts, though it never names a sibling to route away from.

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 an explicit usage constraint — do not automatically retry if the response is lost — which is exactly the kind of guidance an agent needs for a non-idempotent create. It does not describe preconditions (e.g., that a file must already be selected in the UI) beyond the passing reference to 'el archivo seleccionado'.

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

All presupuestos.red tools Inspect

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

Need Help?