Skip to main content
Glama

GoCDKeys

by com.gocdkeys
OverviewDiscussionsAdmin

search_game

Busca un juego por nombre y devuelve su id, las plataformas en las que existe y su ficha. Cada precio trae precio_base (sin tasas de pago) y precio_con_tasas: citalos juntos y con su formato, «X EUR (Y EUR con tasas)», o «X EUR (sin tasas)» si tasas es 0. Usalo cuando el usuario mencione un juego y necesites resolverlo antes de pedir precios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesNombre del juego
langNoIdioma del usuario para los enlaces: es, en, de, fr, it o pt. Por defecto en
platformNopc, ps5, ps4, xbox-one, xbox-series, switch o switch-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Idioma del usuario para los enlaces: es, en, de, fr, it o pt. Por defecto en",
+  "type": "string"
+}
    • changedInput schema / properties / platform / description
      Previous value: -"pc, ps5, ps4, xbox-one, switch o switch-2"New value: +"pc, ps5, ps4, xbox-one, xbox-series, switch o switch-2"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields and a price-formatting convention, but says nothing about matching behavior (e.g. multiple/fuzzy results), pricing source, or any auth/rate constraints; for a read-style search tool this is acceptable but not rich.

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

Conciseness4/5

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

Front-loads what the tool does, then the return shape, then the usage trigger, with no filler sentences. The price-formatting directive is dense and slightly verbose, keeping it from a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly summarizes the return shape (id, platforms, ficha) and even specifies how to render base vs. with-fees prices. Combined with the usage trigger, an agent has everything needed to call and report this tool correctly.

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 q, lang and platform are already documented in the schema. The description adds no additional parameter meaning beyond the schema (the price-format text concerns output, not inputs), which matches the baseline 3 for high-coverage schemas.

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?

States a specific verb (Busca) plus resource (un juego por nombre) and defines the return payload (id, plataformas, ficha). Crucially it positions itself relative to siblings as the resolver step performed before asking for prices, so an agent can distinguish it from get_best_price/get_deals 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 Guidelines4/5

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

Explicitly says to use it 'cuando el usuario mencione un juego y necesites resolverlo antes de pedir precios', which gives a clear trigger and an implied ordering relative to get_best_price. It does not name an alternative to avoid, so it stops short of full when/when-not guidance.

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

All GoCDKeys 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