Skip to main content
Glama

mister_search

Read-only

Search for a game by words from its title to locate it on MiSTer before launch.

Instructions

Find a game by its name. Name: words from the game's title, as the owner said them.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe lookup, so the description isn't carrying the safety burden. It does add one useful behavioral nuance in 'as the owner said them,' hinting that matching is against the title as recorded by the owner rather than an exact canonical string. It says nothing about behavior when no match is found or about match breadth.

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?

Two short sentences, front-loaded with the action. The second sentence is slightly awkwardly phrased and restates the parameter name, but nothing is bloated or buried.

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?

The tool is simple (one required parameter) and an output schema exists, so return values needn't be explained. Still, for a search tool the definition omits what a successful or empty result means and gives no hint about using the result with mister_launch, 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 coverage is 0% and the schema only labels the field 'Name: string', so the description has to supply meaning — and it partly does, clarifying that the value should be words from the game's title rather than an ID or exact full title. It remains ambiguous on partial-word matching, case sensitivity, and what happens with near-miss titles.

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 verb and resource: 'Find a game by its name.' An agent can tell this is a lookup/search operation, not a launch or update. It stops short of differentiating itself from siblings like mister_launch or mister_status, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives. The only implied guidance is that this is how you locate a game before acting on it, which the agent must infer from the purpose sentence alone.

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