Skip to main content
Glama

Peek at public game numbers

world_peek
Read-only

Public, aggregated numbers of Space-Core before you have an account: pilots active in the last 5 minutes (including the game's own AI pilots), trades and fights won in a fixed 60-minute window that ended at least 5 minutes ago, number of sectors and the Raw Titanium list price. No player names; values below 3 are only shown as "fewer than 3". Needs no token and is not tied to any account; changes nothing in the game (only an anonymous rate counter). Numbers are refreshed at most once per minute, older numbers are marked as such. Followed by how to get an account. Optional language: de or en.

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

Input Schema

NameRequiredDescriptionDefault
languageNode or en (default: language from ?lang, otherwise de)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, and the description still adds substantial context beyond them: no token or account binding, a side effect limited to an anonymous rate counter, refresh cadence of at most once per minute with stale values marked, and a privacy rule suppressing counts below 3 and omitting player names. These are exactly the operational traits an agent needs before calling an unfamiliar public endpoint.

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 payload metrics are front-loaded in the first sentence and the operational caveats follow logically. It is dense and slightly run-on, and the trailing 'Optional language: de or en' duplicates the schema, but no sentence is filler.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it lists each reported metric, the time windows, the privacy masking, and the freshness marking. Combined with the zero-required-parameter schema and restrictive annotations, nothing material is left unspecified.

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% and the single optional 'language' parameter already documents the 'de or en' values and the ?lang fallback. The description's 'Optional language: de or en' merely restates the schema, adding no new meaning, so the 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?

The description names a specific resource (public aggregated game numbers) and enumerates exactly what is returned: pilots active in the last 5 minutes including AI pilots, trades and fights won over a fixed 60-minute window, sector count, and Raw Titanium list price. It also states the scoping condition 'before you have an account', which separates it from the account-bound siblings such as get_status or get_market.

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?

It clearly frames the audience and context: use this when you have no account, since it 'Needs no token and is not tied to any account', and it notes the response ends with how to obtain an account. It does not explicitly name an alternative tool for the authenticated case, so the routing is implied rather than spelled out.

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