Skip to main content
Glama
Sign In

INPUT · buscador

by ink.input
OverviewDiscussionsAdmin

Buscar juegos argentinos

buscar_juegos

Busca en el catálogo de juegos hechos en Argentina por título, estudio o género. Devuelve título, estudio, etapa, plataformas, si es gratis y el link para jugar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_juegos"
  }
}

Input Schema

NameRequiredDescriptionDefault
gratisNoSolo los gratis.
limiteNoCantidad máxima de resultados (por defecto 8).
consultaNoTítulo, estudio o género.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations the description must carry the behavioral load; it partially does by disclosing the returned fields (título, estudio, etapa, plataformas, gratis, link). It says nothing about matching semantics (exact vs partial), result ordering, or what happens when nothing matches.

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?

Two sentences, no filler: the search scope comes first and the return payload second. Every clause carries information the agent needs.

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 3-param, zero-required search tool with no output schema, the description substitutes reasonably well by listing the return fields. Only the absence of any mention of empty-result behavior or the sibling tools keeps it from full completeness.

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 description coverage is 100%, so the three parameters are already documented. The description only restates the searchable fields for 'consulta' and never explains 'gratis' or 'limite' beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (busca) and resource (catálogo de juegos hechos en Argentina) and enumerates the searchable fields (título, estudio, género). Against siblings buscar_discos/buscar_lugares/buscar_notas the distinguishing resource is unmistakable, so an agent can route without opening any schema.

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?

Implies its use case (free-text catalog lookup across three fields) but gives no explicit when-to-use/when-not guidance and never mentions the sibling search tools or how to choose among them. Adequate but inferential.

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

All INPUT · buscador toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources