Skip to main content
Glama

get_action_log

Read-onlyIdempotent

Retrieve your or your faction's persistent action history (Returns logged events newest-first. Optional category filter: combat, trading, ship, crafting, faction, mission, skill, salvage, storage, achievement, mining, navigation, exploration, reputation, drone, session, other. Optional event_type filter for one exact event (e.g. "faction.production_cycle" to see only a faction's production-run history, or "combat.ship_plundered" for what pirates or another player took when they plundered your ship) or an array of event_types to match any of them. Optional faction_id to view faction log. Page-based pagination (page, page_size, max 100 entries per page). For incremental polling, pass a positive since_id instead of page: returns entries with greater IDs in ascending ID order, up to page_size. Pass next_since_id on the next poll; keep the current cursor if it is absent. If archive reads fail, the request returns an error; retry the same since_id. Concurrent writes can appear later with lower IDs, so use recent page-based history to reconcile missed entries. Recent history is served live; older history is retained in long-term storage. Tolls and holds log to both pilots: trading.offer_sent and trading.offer_received carry credits (the toll asked), offer_safe_passage and hold; trading.toll_paid carries credits (what was paid), request_credits and until_tick; trading.toll_expired carries credits 0; combat.hold_started and combat.hold_ended (with reason) carry holder_id, target_id, trade_id and start_tick; combat.safe_passage_granted carries the credits paid; combat.hold_started and combat.hold_ended also carry source (toll or scan). Cargo scans log combat.cargo_scan_completed (target_id, scan_power, items: the cargo read) or combat.cargo_scan_failed (target_id, scan_power, reason) for the scanner, and combat.cargo_scan_detected (scanner_id, empty for a cloaked scanner, and held_ticks, 0 without a hold) for the target. A player plunder logs combat.ship_plundered for the victim (attacker_id, attacker_name, ship_id, system_id, boarding_op_id, surrendered, items, total_value) and combat.plunder_completed for the robber (target_id, ship_id, system_id, boarding_op_id, items with item_id/quantity/value, total_value in credits, overflow_units: units left aboard for lack of hold space), and combat.safe_passage_granted (source robbery, credits 0) for both.)

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1). Ignored when since_id is set.
categoryNoFilter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, storage, achievement, mining, navigation, exploration, reputation, drone, session, other)
since_idNoPositive cursor: return entries with greater IDs in ascending ID order, up to page_size. Pass 0 or omit for newest-first paging. Pass next_since_id on the next poll; keep the current cursor if it is absent. If archive reads fail, the request returns an error; retry the same since_id. Concurrent writes can appear later with lower IDs, so use recent page-based history to reconcile missed entries.
page_sizeNoEntries per page, or max entries to return when since_id is set (default 50, max 100)
event_typeNoFilter to an exact event_type (e.g. faction.production_cycle for faction production-run history), or an array of event_types to match any of them
faction_idNoView a faction's action log instead of your own (must be a member)
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / since_id / description
      Previous value: -"Cursor for gap-free incremental polling: return only entries with id greater than this, oldest-first, up to page_size. Pass 0 or omit for normal newest-first paging. Pass the response's next_since_id on your next poll to continue exactly where you left off."New value: +"Positive cursor: return entries with greater IDs in ascending ID order, up to page_size. Pass 0 or omit for newest-first paging. Pass next_since_id on the next poll; keep the current cursor if it is absent. If archive reads fail, the request returns an error; retry the same since_id. Concurrent writes can appear later with lower IDs, so use recent page-based history to reconcile missed entries."
  2. Added
  3. Removed
  4. Changed6 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, storage, other)"New value: +"Filter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, storage, achievement, mining, navigation, exploration, reputation, drone, session, other)"
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "combat",
      -  "trading",
      -  "ship",
      -  "crafting",
      -  "faction",
      -  "mission",
      -  "skill",
      -  "salvage",
      -  "storage",
      -  "other"
      -]New value: +[
      +  "combat",
      +  "trading",
      +  "ship",
      +  "crafting",
      +  "faction",
      +  "mission",
      +  "skill",
      +  "salvage",
      +  "storage",
      +  "achievement",
      +  "mining",
      +  "navigation",
      +  "exploration",
      +  "reputation",
      +  "drone",
      +  "session",
      +  "other"
      +]
    • addedInput schema / properties / event_type
      Added value: +{
      +  "description": "Filter to an exact event_type (e.g. faction.production_cycle for faction production-run history), or an array of event_types to match any of them",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "string",
      +    "array"
      +  ]
      +}
    • changedInput schema / properties / page / description
      Previous value: -"Page number (default 1)"New value: +"Page number (default 1). Ignored when since_id is set."
    • changedInput schema / properties / page_size / description
      Previous value: -"Entries per page (default 50, max 100)"New value: +"Entries per page, or max entries to return when since_id is set (default 50, max 100)"
    • addedInput schema / properties / since_id
      Added value: +{
      +  "description": "Cursor for gap-free incremental polling: return only entries with id greater than this, oldest-first, up to page_size. Pass 0 or omit for normal newest-first paging. Pass the response's next_since_id on your next poll to continue exactly where you left off.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  5. Changed7 schema fields changed
    • removedInput schema / properties / before
      Removed value: -{
      -  "description": "RFC3339 timestamp for cursor-based pagination - get entries before this time",
      -  "type": "string"
      -}
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, other)"New value: +"Filter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, storage, other)"
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "combat",
      -  "trading",
      -  "ship",
      -  "crafting",
      -  "faction",
      -  "mission",
      -  "skill",
      -  "salvage",
      -  "other"
      -]New value: +[
      +  "combat",
      +  "trading",
      +  "ship",
      +  "crafting",
      +  "faction",
      +  "mission",
      +  "skill",
      +  "salvage",
      +  "storage",
      +  "other"
      +]
    • addedInput schema / properties / faction_id
      Added value: +{
      +  "description": "View a faction's action log instead of your own (must be a member)",
      +  "type": "string"
      +}
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max entries to return (default 50, max 100)",
      -  "maximum": 100,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page number (default 1)",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page_size
      Added value: +{
      +  "description": "Entries per page (default 50, max 100)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  6. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly and idempotent; the description adds substantial behavior the agent could not infer — live vs long-term storage split, error-and-retry semantics when archive reads fail, and the warning that concurrent writes can surface later with lower IDs. It also documents what specific log event types contain, which matters because no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core usage guidance is front-loaded and efficient, but the second half degenerates into a long run-on catalog of event payloads in nested parentheses. Those details are useful given the absent output schema, yet they are poorly structured and would be far more scannable as a list.

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?

For a 7-parameter log tool with no output schema, the description covers ordering, pagination modes, cursor handling, retention tiers, failure behavior, and per-event payload fields. An agent has enough to call it correctly and interpret results without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does duplicate some pagination wording already present in the since_id schema text. It earns above baseline by giving semantic examples of event_type values (faction.production_cycle for production-run history, combat.ship_plundered for what a robber took) that the schema does not explain.

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 ('Retrieve your or your faction's persistent action history') plus scope qualifiers — persistent, own vs faction, newest-first ordering. An agent can distinguish this from get_battle_log or captains_log_list without opening the 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 explicit conditional guidance: use category or event_type to narrow, faction_id to view a faction log, since_id instead of page for incremental polling, and reconcile missed entries via recent page-based history. It never explicitly names a sibling tool or says when not to use this one, which keeps it below a 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