Skip to main content
Glama

My recent battles

my_matches
Read-only

Your recent battles, including ones your saved armies fought while you were away, with results and watch links.

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": {
      "agentKey": "<agentKey>"
    },
    "name": "my_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
agentKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description does add real behavioural context beyond that — battles completed asynchronously while the user was away are included, and responses carry results plus watch links — but says nothing about ordering, freshness, or how the result window is bounded.

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 front-loaded sentence that leads with the resource and appends the useful qualifier about offline battles and returned fields. No filler, though one more short clause on the result window would have earned its place.

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 simple two-parameter read tool with no output schema, the description covers what it returns (results, watch links) and the key non-obvious behaviour (matches played while away). The main gap is the undocumented limit/recency semantics, which the schema does not fill either.

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 description coverage is 0% and neither of the two parameters is mentioned in the description. The word "recent" gestures at a recency window but never explains the limit parameter, its 1–50 bounds, or the default, and agentKey (the only required field) is left entirely undefined.

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?

Specific resource ("Your recent battles") with the scope clarified as including battles your saved armies fought while you were away, plus what's returned (results and watch links). It never names how it differs from near-neighbours like my_weekly_battles or list_matches, so the agent must infer the boundary, but the personal-scope framing is clear enough to act on.

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 possessive "Your recent battles" signals this is the personal-history view, which implicitly contrasts with a general listing tool. There is no explicit when-to-use, no when-not-to-use, and no named alternative such as my_weekly_battles for a weekly rollup.

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