Skip to main content
Glama

games_results

Read-only

Finds game, game studio and collection pages by matching the given text against page names. Descriptions, topics and themes lie outside its scope. Review count: 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": {
      "q": "<q>"
    },
    "name": "games_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesA game, studio or collection title, or a fragment of one, containing two or more characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 and openness profile is covered structurally. The description adds useful scope constraints but says nothing about matching semantics (prefix vs substring), result ordering, or result volume. The trailing 'Review count: 10' fragment is opaque and does not clearly communicate behavior, which weakens rather than strengthens transparency.

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 key scope exclusion. The dangling 'Review count: 10' has no clear referent and consumes attention without earning its place, which drags the structure down from what would otherwise be a 4.

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?

With one required parameter, full schema coverage, and annotations covering safety, this is a simple tool that needs little explanation. Scope exclusions are stated well; only the return shape (fields per hit) and the cryptic review-count fragment leave an agent with open questions.

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 parameter's schema already states it is a title or fragment of at least two characters. The description's 'matching the given text against page names' reinforces the match field but adds no syntax, casing, or normalization detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource set: 'Finds game, game studio and collection pages,' and immediately narrows the match target to page names. That is enough for an agent to understand what the tool returns. It does not explicitly differentiate itself from the siblings online_games and top_games, so it falls short of a 5.

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?

The line 'Descriptions, topics and themes lie outside its scope' gives concrete when-not-to-use guidance, which is the main failure mode for a text-search tool. However, it never points to an alternative for those excluded cases, so routing is left to inference.

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