Game Stats AI

find_character

Read-only

Look up a character (a card, unit, or character is the same thing here) by name and return a summary: matches played, the version it was first seen in, when it was last played, and its 5 most recent matches (match ids for get_match). If several characters match, returns the candidates so you can ask the user which one.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	The character's name or part of it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the description's job is to add operational detail, which it does: partial-name matching, a 5-match cap, and a candidate-list fallback instead of arbitrary selection. It leaves unstated what happens on zero matches and whether matching is case-sensitive.

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?

Two sentences, zero filler. The parenthetical terminology gloss is front-loaded, the return payload is enumerated compactly, and the ambiguity case is saved for last where it belongs.

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 no output schema, the description carries the return-value burden and does so well, naming each summary field and the recent-matches slice. The one omission for a lookup tool is the no-match case, which an agent will eventually hit.

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 baseline would be 3, but the description adds real meaning by explaining the consequence of the fuzzy 'name or part of it' parameter — multiple matches yield a candidate list rather than one result. That is behavior the schema does not convey.

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?

Names a specific verb and resource ("look up a character... by name") and preemptively disambiguates domain vocabulary by equating card, unit, and character. It also enumerates exactly what the summary contains, so an agent knows the shape of the result without opening any schema.

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?

Explicitly routes the agent forward: the returned match ids are labeled "for get_match", which tells the agent how to continue. The ambiguous-name branch also instructs the agent to ask the user rather than guess. It stops short of distinguishing itself from nearby siblings like get_character_report or list_top_characters.

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

All Game Stats AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?