Skip to main content
Glama

Wisely Arcade Games

search_games

Search Wisely Arcade games by keyword — matches titles, descriptions, lessons and skills.

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

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword or phrase to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It usefully discloses which fields are searched (titles, descriptions, lessons, skills), but says nothing about result limits, ordering/relevance, or case sensitivity — gaps that matter for a search tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the scope stated first and the matching fields after the dash. There is no filler and nothing to trim.

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 search tool with no annotations and no output schema, the description covers what is searched and that this is keyword-based, which is enough to call it correctly. It could say more about result shape or limits, though with no output schema that omission is forgivable.

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%, so the baseline is 3, but the description genuinely adds meaning by explaining that the query string is matched against titles, descriptions, lessons, and skills rather than one field. It stops short of describing matching rules (substring vs. fuzzy, multi-word behavior).

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 names a specific verb and resource ("Search Wisely Arcade games") and scopes it to keyword matching, which separates it from a plain enumeration like list_games. It does not explicitly name a sibling or contrast behavior, so it falls just 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 Guidelines3/5

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

Usage is only implied: the phrase "by keyword" signals a text-query entry point, but nothing states when to prefer this over list_games or get_game, or what to do when there is no keyword. An agent must infer the routing itself.

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.