Skip to main content
Glama

buscar_giros

Read-only

Herramienta que localiza páginas de juegos, de estudios de juegos y de colecciones cuyo nombre contiene el texto dado. No contempla búsquedas por tema ni por descripción. Total de análisis: 21

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": {
      "q": "<q>"
    },
    "name": "buscar_giros"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFragmento del nombre de un juego, estudio de juegos o colección, de al menos dos caracteres de longitud.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds only that matching is on a name fragment; it says nothing about result ordering, pagination, or whether matches are partial-word or prefix. The trailing 'Total de análisis: 21' is opaque and conveys no actionable behavior.

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 first two sentences are tight and front-loaded, stating purpose then exclusions. The third sentence, 'Total de análisis: 21', reads as stray metadata that does not earn its place and slightly muddies an otherwise clean definition.

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?

For a one-parameter read-only lookup with full schema coverage, annotations and no output schema, the essentials are present. Still missing is any indication of what a match returns (pages, collections, mixed types) and what the unexplained 'Total de análisis' figure refers to.

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% and the q parameter already documents itself as a name fragment of at least two characters. The description reinforces the substring-on-name semantics and confirms the fragment never applies to descriptions or themes, which is a modest but genuine addition beyond 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 (localiza páginas) and enumerates the three resource types searched: juegos, estudios de juegos and colecciones, with matching on name substring. It is clear what the tool retrieves, though it never references the sibling tools juegos_online or maquinas_populares to sharpen the boundary.

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 an explicit negative constraint: no searches by theme or description, only by name. This is real when-not guidance, but it names no alternative tool for the excluded cases, leaving the agent to guess where to route a thematic query.

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