Skip to main content
Glama

busqueda

Read-only

Encuentra páginas de juegos, estudios de juegos y colecciones cuyo nombre incluya el texto escrito. El tema y la descripción quedan fuera de la búsqueda. Reseñas de juegos: 10

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": {
      "termino": "<termino>"
    },
    "name": "busqueda"
  }
}

Input Schema

NameRequiredDescriptionDefault
terminoYesFragmento 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

B3.3/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 is covered. The description does add real behavioral information — that matching is restricted to names and excludes theme/description — but the cryptic 'Reseñas de juegos: 10' gives no clear meaning (result limit? review count?), so it neither informs nor verifiably misleads.

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 with the matching rule, but the closing fragment 'Reseñas de juegos: 10' is dangling and unparsable, adding noise rather than information.

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 search tool with full schema coverage and no output schema, the essentials are present — what is matched and what is not. However, it never indicates result behavior (limits, ordering, number of results returned), and the ambiguous trailing item hints at a limit without explaining it.

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 single 'termino' parameter is already documented as a 2-64 character name fragment with a required constraint. The description only restates that it matches names, adding the scoping caveat but no new syntax or format detail, so 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?

The description opens with a concrete verb ('Encuentra') and names exactly the resource types searched (páginas de juegos, estudios de juegos, colecciones), plus the field matched (nombre). An agent can tell it is a name-substring search rather than a general lookup, though the trailing 'Reseñas de juegos: 10' fragment muddies the stated scope.

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

Usage Guidelines3/5

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

Usage is implied rather than prescribed: 'El tema y la descripción quedan fuera de la búsqueda' is a useful negative constraint that tells the agent what this search cannot find, but there is no explicit when-to-use framing and no named alternative among siblings (maquinas, top_giros).

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