Skip to main content
Glama

lookup_machines

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: 24

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": {
      "s": "<s>"
    },
    "name": "lookup_machines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesFull or partial name of a game, game studio or collection, at least two characters long.

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 safety profile is covered. The description contributes genuinely non-obvious behavior: matching is confined to page names, not body text, which prevents an agent from guessing this is a general search endpoint. It says nothing about result ordering, pagination, or empty-match behavior.

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 well-structured and front-load the scope and its exclusion. The trailing "Review count: 24" is unexplained metadata that does not help an agent select or invoke the tool, so one of three sentences fails to earn its place.

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 one-parameter lookup with no output schema and annotation coverage for safety, the description supplies what matters: what is searched, what is not, and what the string may denote. Remaining gaps (result shape, ordering, limits on returned matches) are modest given the tool's simplicity.

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 coverage is 100% and the single parameter is already documented with type and 2-64 length bounds. The description adds a small amount of meaning by clarifying that partial names are acceptable and enumerating the entity types the string can refer to, but this largely restates the schema. Baseline 3 is appropriate.

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?

The description names a specific verb ("Finds") and a precise resource set (game, game studio and collection pages), then states the matching mechanism: text matched against page names. It immediately dispels the most likely misread by declaring that descriptions, topics and themes are outside its scope.

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?

It gives a clear negative boundary (not a full-text search over descriptions/topics/themes), which tells an agent exactly when this tool will fail. It stops short of naming an alternative tool to use for those body-text searches, so the routing guidance is one-sided rather than complete.

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