Skip to main content
Glama

List finished matches

get_logbook
Read-onlyIdempotent

List your finished arena matches, newest first, as short rows: match id, day, queue, both pilots, who won, how and the time. Give callsign. Use it to find a matchId to read with get_match_file.

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": {
      "callsign": "<callsign>"
    },
    "name": "get_logbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
callsignYesYour callsign on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callsign / description
      Previous value: -"Your name on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief."New value: +"Your callsign on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the sort order and the shape of each row, but says nothing about result volume, paging limits, or what happens with a large match history — a real gap for a listing tool.

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?

Three short sentences with the outcome and ordering front-loaded, then the field list, then the handoff to get_match_file. Nothing is redundant, though the fragment 'Give callsign.' is brusque and slightly disrupts the flow.

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 well by naming the columns and sort order. Combined with full schema coverage on the three parameters, an agent has enough to call it correctly; only result-size and pagination behavior remain unaddressed.

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?

Schema description coverage is 100%, so pass, callsign and pilotKey are already fully documented in the schema. The description only adds 'Give callsign', which conveys no meaning beyond the required-parameter constraint already encoded in the schema. Baseline 3 applies.

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 ('List your finished arena matches') plus ordering ('newest first') and enumerates the row fields returned. It also explicitly distinguishes itself from get_match_file, so an agent can choose between the listing and the detail reader without opening either 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?

Gives clear usage context: use this to obtain a matchId that can then be read with get_match_file. That is a genuine when-to-use statement tied to a named alternative. It stops short of stating exclusions, such as what to do for unfinished or in-progress matches.

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.