Skip to main content
Glama

Find players

find_players
Read-onlyIdempotent

Find a player to gift, the same search as the shop's gift window: players in any kingdom whose name contains your query (names that start with it first), with account_id, kingdom, alliance tag and whether they're an AI. With no query: suggestions (people you gifted before, your alliance, your DMs).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNopart of a display name (2+ characters); leave empty for suggestions: people you gifted, your alliance, your DMs
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low; the description still adds substantive behavior: substring matching across all kingdoms, prefix-first ordering, the exact fields returned (account_id, kingdom, alliance tag, AI flag), and the empty-query fallback. That is ranking and result-shape information an agent cannot get from the annotations.

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 sentences, purpose and scope front-loaded, no filler. The heavy use of nested parentheses (matching rule, returned fields, suggestion sources) makes it dense to parse, though every clause carries real information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully documented search tool with an output schema, this covers everything an agent needs: matching semantics, ranking, the zero-argument fallback, and the data fields returned. Nothing material about invoking it correctly is left unstated.

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 is 3, but the description goes further by explaining the matching rule for 'query' (contains, with starts-with ranked first, any kingdom) and reiterating the empty-query suggestion behavior with its sources. It adds ordering semantics the schema does not state; the 'token' parameter's retry condition is only documented in the schema.

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?

States a specific verb and resource ('Find a player to gift') and immediately pins down the scope: players in any kingdom whose name contains the query, prefix matches ranked first. It even names the reference behavior ('the same search as the shop's gift window'), so an agent knows exactly which operation this mirrors and can distinguish it from siblings like gift_pack or postcard.

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?

The description makes the use case explicit (locating a recipient before gifting) and gives a clear second mode: call with no query to get suggestions drawn from past gifts, alliance, and DMs. It stops short of explicitly naming an alternative tool or a when-not-to-use condition, but the two modes cover the practical decision space.

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