Skip to main content
Glama

machines_search

Read-only

Matches pages of games, game studios and collections by name only; the given text is not looked for in themes or descriptions. Number of game reviews: 14

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

Input Schema

NameRequiredDescriptionDefault
qYesThe name of a game, a studio or a collection, or part of that name, with a minimum of two characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 safety and closed-world scope are covered. The description usefully adds that matching is name-only, but the trailing sentence 'Number of game reviews: 14' is an unexplained statistic unrelated to invocation behavior and reads as noise rather than disclosure.

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 information-dense. The second sentence about review counts is disconnected from the tool's purpose and does not earn its place, weakening 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, the definition covers the matching semantics well. It does not describe what the result set looks like — whether games, studios and collections come back mixed, or what fields each carries — which an agent would need since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'q' parameter is fully documented with length bounds. The description still adds value beyond the schema by clarifying what the string is matched against (names of games, studios, collections) and explicitly excluding themes and descriptions as match targets.

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 states a specific action and resource set: it matches 'pages of games, game studios and collections' and scopes the match to names. An agent can tell this is a name-lookup search rather than a browsing tool, though no sibling is named for contrast.

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?

It gives one useful usage constraint — the query text is NOT searched in themes or descriptions — which implicitly tells the agent to look elsewhere for thematic search. However, it never names an alternative tool or states when this tool should be preferred over the sibling 'games' tool, leaving routing 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