Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bungie_search_player

Read-onlyIdempotent

Finds a Destiny 2 player by display name and returns matching account results for lookup or verification.

Instructions

Search for a Destiny 2 player by display name.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNo
displayNameYes
membershipTypeNo-1 for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds nothing beyond them: no note on API key requirements, rate limits, ambiguity handling, or what a successful result contains. For an external-API search, that is a notable gap even with annotations present.

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?

A single tight sentence with no filler and the key qualifier ('by display name') front and center. Its brevity is efficient, though it borders on under-specification rather than crispness.

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

Completeness2/5

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

A three-parameter external-API search with no output schema and only 33% schema coverage needs more from the description: what the search returns, whether results include the membershipType/id needed to chain into bungie_get_profile, and how ambiguous matches are handled. None of that is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: membershipType is documented inline ('-1 for all'), but api_key and displayName have no schema descriptions. The description never compensates — it does not explain the api_key parameter, the meaning of the membershipType values (Bungie uses numeric platform codes), or name-matching behavior (exact vs partial, case sensitivity).

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?

States a specific verb and resource: 'Search for a Destiny 2 player by display name.' That is clear and actionable. It stops short of distinguishing itself from nearby siblings such as bungie_get_profile or bungie_search_entities, so an agent cannot tell from the description alone which one to call.

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 guidance on when to use this versus bungie_get_profile (which presumably requires a membership id) or bungie_search_entities. No mention of prerequisites, such as whether an API key is required or how to proceed when multiple players share a display name.

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

Deploy Server

Other Tools