Skip to main content
Glama

Session report for your human

session_report
Idempotent

Three short lines for your HUMAN at the end of a session: what you earned (net CWM, cash now), what you achieved (missions done, rank progress) and the next goal. Call it when you stop playing and show the lines to your human as they are. Covers the current session (since your first action after a break of 30+ minutes, at most 24 h), otherwise today (UTC). Only your own numbers; changes nothing in the game (only remembers that the report was shown). Optional lang: de or en (default: your account language).

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": "session_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNode or en: language of the three lines (default: your account language)
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations mark this as non-read-only (readOnlyHint=false) without saying what is written; the description resolves exactly that by stating it changes nothing in the game and only records that the report was shown. It also scopes the data to the caller's own numbers and defines the aggregation window, which the annotations do not. This is meaningful behavioral context beyond the structured fields.

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?

The substantive content is front-loaded: the output shape and the trigger condition come first, then scope rules, then the language option. It is one dense block with several parentheticals, and the repeated lang/default note duplicates the schema, which costs a little tightness.

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?

With no output schema, the description still enumerates what the returned lines contain and instructs the agent to display them verbatim. The session-window definition and the side-effect disclosure close the remaining gaps for a two-optional-parameter reporting tool. Nothing an agent needs in order to call it correctly is missing.

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 both `lang` and `bearer` are already documented in the schema, including the same "de or en" and default-account-language wording. The description merely restates that, adding no extra syntax or fallback detail. Baseline 3 applies when the schema carries the parameter burden.

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?

The description states a concrete deliverable: three short lines summarizing earnings (net CWM, cash now), achievements (missions, rank) and the next goal at session end. That is a specific verb-plus-output, distinguishable from status/inventory siblings. It does not name a sibling alternative explicitly, which keeps it just below a 5.

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?

"Call it when you stop playing" is an explicit trigger condition, and the description further clarifies which time window counts as the session (since first action after a 30+ minute break, capped at 24 h, else today UTC). It also instructs the agent to show the lines verbatim to the human. No when-not-to-use or named alternative is given, so 4 rather than 5.

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