Skip to main content
Glama

search

Read-only

Returns every page of a game, a game studio or a collection whose name contains the given text. Searching by topic, theme or description is not supported. Number of game reviews: 19

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

Input Schema

NameRequiredDescriptionDefault
qYesTwo or more characters from the name of a game, a game studio or a collection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is to add retrieval behavior. It does: results are exhaustive ('returns every page'), meaning the agent needn't paginate, and the name-only matching constraint is disclosed. It omits result shape, ordering and error behavior.

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?

The core behavior and the exclusion are front-loaded in two tight sentences. The trailing 'Number of game reviews: 19' is an unexplained appended stat that does not clearly serve query or interpretation guidance.

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 tool with annotations and no output schema, the description covers scope and exhaustiveness adequately. However, with no output schema it never indicates what a returned page/entity looks like or how many results to expect, leaving a modest 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?

Schema description coverage is 100% and the single 'q' parameter already documents the 2-64 character rule. The description restates the same name-substring semantics without adding syntax, normalization or escaping detail, so it is baseline-equivalent to the schema.

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 retrieval verb and the three resource types searched (game, game studio, collection) plus the matching rule ('name contains the given text'). The negative clause about topic/theme/description matching further pins down what the tool is, so an agent can distinguish it from a general search.

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?

Gives an explicit 'when not to use' condition: searching by topic, theme or description is unsupported, which steers the agent away from a wrong query strategy. No alternative tool is named, so the guidance stops short of full routing.

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