Skip to main content
Glama
Sign In
automeli-docs-mcp

automeli-docs-mcp

Official
by Automeli-Services-Organization
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar en la doc

search_docs
Read-only

Search Automeli API documentation for endpoints, errors, guides, and flows; get ranked results with type, title, reference, and excerpt to answer integration questions.

Instructions

Búsqueda léxica en toda la documentación: endpoints, errores, guías y flujos. Devuelve resultados rankeados con tipo, título, referencia (operationId / código de error / URL) y un extracto. Útil para '¿cómo publico un producto?', 'rate limit', 'cursor', 'idempotencia', etc.

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": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo de resultados (default 8).
queryYesTexto a buscar, ej. 'paginación por cursor', 'créditos', 'E_RATE_LIMITED'.
versionNoVersión de la API a consultar. Default "v2" (la doc canónica y recomendada). Usá "v1" SOLO para integraciones legadas que siguen en /api/v1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, lowering the disclosure bar. The description adds useful context beyond them: results are returned ranked with type, title, a reference (operationId / error code / URL) and an excerpt, and the search is lexical rather than semantic. No pagination or ranking-order caveats, but the core behavior is well conveyed.

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?

Three sentences, front-loaded with the search scope, then return shape, then example intents. Efficient and free of filler, though the example-query list is slightly loose prose.

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?

No output schema exists, but the description compensates by describing the result fields and ranking, and the parameter schema is fully documented. An agent has enough to call it and interpret results; only sibling routing is 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, limit, and version (including the v2-default / v1-legacy guidance and enum). The description adds nothing parameter-specific beyond the return fields, so the baseline 3 applies.

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+resource: 'Búsqueda léxica en toda la documentación' and enumerates the coverage (endpoints, errores, guías, flujos). The lexical qualifier helps an agent distinguish it from semantic or targeted lookups, but it never names or contrasts any sibling (e.g., get_endpoint or explain_error) for direct lookups.

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?

"Útil para '¿cómo publico un producto?', 'rate limit', 'cursor', 'idempotencia'" gives concrete query intents, which clarifies when to reach for this tool. It stops short of stating when NOT to use it or which sibling covers narrower needs (single endpoint detail, error explanation).

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

Deploy Server

Other Tools