Ecuafact API · Documentación

consultar_referencia

Read-onlyIdempotent

Consulta el contrato OpenAPI del API. Sin ruta, lista los endpoints. Con ruta (y metodo), devuelve los parametros, el cuerpo, las respuestas y los esquemas que usa.

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

Input Schema

Name	Required	Description	Default
`ruta`	No	Ruta del endpoint como aparece en el listado. La emision usa una ruta por tipo de comprobante, por ejemplo '/v1/contribuyentes/{identificacion}/facturas' o '/v1/contribuyentes/{identificacion}/notas-credito' (opcional).
`metodo`	No	Metodo HTTP: GET, POST o PUT (opcional; por defecto el unico o el primero).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedInput schema / properties / metodo / description

Previous value: -"Metodo HTTP: GET, POST, PUT o DELETE (opcional; por defecto el unico o el primero)."New value: +"Metodo HTTP: GET, POST o PUT (opcional; por defecto el unico o el primero)."

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / ruta / description

Previous value: -"Ruta del endpoint como aparece en el listado, por ejemplo '/v1/contribuyentes/{identificacion}/comprobantes' (opcional)."New value: +"Ruta del endpoint como aparece en el listado. La emision usa una ruta por tipo de comprobante, por ejemplo '/v1/contribuyentes/{identificacion}/facturas' o '/v1/contribuyentes/{identificacion}/notas-credito' (opcional)."

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety is covered. The description goes further by disclosing exactly what each invocation mode returns (endpoint list, or parameters/body/responses/schemas), which is the key behavioral fact an agent needs; it says nothing about response size or ordering.

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?

Two short sentences with the resource first and the two modes front-loaded; every clause carries information and there is no 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?

For a two-optional-parameter, read-only lookup with no output schema, the description covers both invocation modes and what is returned. Only minor gaps remain, such as whether the endpoint listing is exhaustive or ordered, which rarely affects a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: dropping 'ruta' switches the tool from detail retrieval to a catalog listing, and 'metodo' is only meaningful in combination with 'ruta'. That conditional relationship is the semantic contribution the schema alone does not convey.

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: 'Consulta el contrato OpenAPI del API', and clarifies the two output modes (endpoint listing vs. full operation detail). The purpose is unambiguous, though it does not explicitly differentiate itself from documentation-oriented siblings such as buscar_documentacion or leer_guia.

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?

Provides clear conditional usage: omit 'ruta' to list endpoints, supply 'ruta' (optionally with 'metodo') to retrieve parameters, body, responses and schemas. It does not state when to prefer this over the sibling documentation tools or note prerequisites, but the mode selection is fully spelled out.

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

All Ecuafact API · Documentación 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?