Skip to main content
Glama

critics.press

buscar_textos

Read-onlyIdempotent

Search critics.press pieces by words (title, subtitle and text), in any of the three languages. Busca nos textos do critics.press.

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": {
      "busca": "<busca>"
    },
    "name": "buscar_textos"
  }
}

Input Schema

NameRequiredDescriptionDefault
buscaYesWords to search (accents optional).
limiteNoDefault 10, max 30.
linguaNoOptional: only this language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 contributes the useful fact that matching spans title, subtitle and body text, but says nothing about result ordering, truncation, or what a match returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English sentence is front-loaded and efficient, but the trailing Portuguese sentence "Busca nos textos do critics.press" restates the same purpose without adding scope, fields, or usage detail. It is short overall, yet one of its two sentences does not earn its place for an English-speaking agent.

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 three-parameter, fully documented search tool with no output schema and rich annotations, the definition covers purpose, searched fields, and language scope. Missing only routing guidance against siblings, which is a minor gap given the tool's simplicity.

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 coverage is 100% with per-parameter descriptions for busca, limite and lingua, so the schema does the heavy lifting. The description's only added semantic is "any of the three languages," which loosely explains the lingua enum that the schema already spells out. Baseline 3 is appropriate.

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?

"Search critics.press pieces by words" gives a specific verb and resource, and the parenthetical (title, subtitle and text) narrows the searched fields, which an agent could not infer from the name alone. It does not distinguish itself from siblings like ler_texto or ultimos_textos, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this keyword search versus the sibling retrieval tools, and no exclusions or prerequisites. The agent must infer from the name that this is the discovery tool rather than a fetch-by-id tool.

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.

Resources