Skip to main content
Glama
Sign In
overwatch-AIO-mcp

overwatch-AIO-mcp

by BK927
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ow_player_get

Read-onlyIdempotent

Retrieve a public Overwatch player's profile and career statistics, optionally filtered by hero, role, or mode, with clear indication of private or missing data.

Instructions

Read a public player profile and filtered career/hero/role statistics; report private and missing data distinctly.

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

Input Schema

NameRequiredDescriptionDefault
heroNo
modeNocompetitive
roleNo
viewNosummary
platformNopc
player_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, openWorld, and non-destructive behavior; the description's 'Read' wording is consistent. It adds behavior about reporting private and missing data distinctly, which goes beyond mere annotation.

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?

One concise sentence that front-loads the main action and resource, then adds the key output behavior. No redundant or filler content.

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 description communicates the core purpose and a key output nuance, but given six parameters and a view enum, it leaves several operational details unexplained. It is adequate but not fully complete without schema descriptions or an output schema reference.

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?

The schema has 0% description coverage, and the description only loosely implies filtered career/hero/role statistics. It does not explicitly explain mode, platform, view enum semantics, or how filtering interacts with parameters, so parameter meaning is only partially supplemented.

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?

The description clearly states the tool reads a public player profile and filtered statistics, and distinguishes it from search-oriented siblings like ow_players_search. The verb and resource are specific and unambiguous.

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 gives useful guidance about public data and distinct handling of private/missing fields. It does not explicitly contrast with sibling tools or enumerate when to use this over search tools, but the public/private distinction provides practical usage context.

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