Skip to main content
Glama

buscar_docs

Read-only

Busca trechos da documentação local da biblioteca. Quando usar: para encontrar instruções e referências da API. Quando não usar: para consultar dados clínicos ou códigos específicos.

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": {
      "texto": "<texto>"
    },
    "name": "buscar_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYes
limiteNo

Output Schema

NameRequiredDescriptionDefault
resultadosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that results are local-documentation excerpts, with no details on result size, ranking, or behavior when no match is found. Against annotated tools this is adequate but thin.

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, front-loaded with the purpose and then split cleanly into when-to-use and when-not-to-use. No sentence is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has only two parameters, and has an output schema, so return values need not be described. However, the description omits any parameter guidance and leaves "documentação local da biblioteca" somewhat vague about scope and freshness. It is minimally complete for invocation but not fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for both parameters, yet it never explains what "texto" should contain or what "limite" controls. A reader can infer that "texto" is a search query, but the meaning, constraints, and default of "limite" are left entirely to 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?

The description states a specific verb and resource: it searches excerpts from the library's local documentation. It does not name a sibling tool, but the exclusion of clinical data and specific codes implicitly distinguishes it from lookup-style siblings such as tuss_lookup or operadora_lookup.

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?

It gives explicit "quando usar" and "quando não usar" sections, covering both the intended case (API instructions and references) and an exclusion (clinical data or specific codes). It stops short of naming the alternative tool to use for the excluded cases, so the routing is clear but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.