Skip to main content
Glama

juegos_busqueda

Read-only

Filtra las páginas de juegos, estudios de juegos y colecciones por coincidencia del nombre con el texto escrito, sin buscar en temas ni descripciones. Reseñas de juegos: 8

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": "juegos_busqueda"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesTexto de búsqueda formado por el nombre, total o parcial, de un juego, un estudio de juegos o una colección, con dos o más caracteres.

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 the safety profile is covered. The description adds genuinely useful behavioral scope: matching is restricted to names and does not touch themes or descriptions. Against that, the closing 'Reseñas de juegos: 8' is unexplained and adds 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 sentence is front-loaded and wastes nothing, delivering scope and exclusion in one pass. The dangling 'Reseñas de juegos: 8' is unexplained noise that appears to be leftover boilerplate and detracts from an otherwise tight 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 search with no output schema and clear annotations, the description covers the essential scope. The cryptic review-related fragment leaves an unresolved signal about what results include, which is the main completeness gap.

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?

With a single parameter at 100% schema description coverage, the schema already documents the length bounds and the expected content. The description restates the same idea ('coincidencia del nombre con el texto escrito') without adding syntax, matching, or normalization details beyond the schema, 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?

The description names a specific verb ('Filtra') and concrete resources (páginas de juegos, estudios de juegos, colecciones), so the agent knows exactly what is being searched. The only retrieval sibling, tragamonedas_online, is a distinct resource, so no explicit differentiation is strictly needed. The trailing fragment 'Reseñas de juegos: 8' muddies the otherwise clear statement.

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?

The phrase 'sin buscar en temas ni descripciones' gives a useful exclusion — this tool is for name lookups, not thematic or descriptive queries — which implicitly tells the agent when not to use it. However, no alternative tool or fallback is named for those thematic searches, and no prerequisites are stated, so guidance is implied rather than explicit.

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