Skip to main content
Glama
Sign In
Spaceship MCP

Spaceship MCP

by Spaceship-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_run_logs

Retrieve the chronological event log for a completed agent run, showing every action taken and result returned.

Instructions

Fetch the full event log for a completed run in chronological order.

Returns every event (start, tool_call, memory_access, completion, error, …) so you can see exactly what the agent did and what it returned.

Args: agent_id: The agent's UUID. execution_id: The execution UUID returned by run_agent.

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": {
      "agent_id": "<agent_id>",
      "execution_id": "<execution_id>"
    },
    "name": "get_run_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
execution_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description details return content (every event type) and purpose. Doesn't mention auth or limits, but sufficient for read operation.

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

Conciseness5/5

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

Three focused sentences plus Args section. Efficient use of words with clear structure.

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?

Covers purpose, return content, and parameter origins. Output schema exists, so detailed return spec not needed. Could mention truncation but not critical.

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 only provides titles; description adds meaning: agent_id is UUID, execution_id is from run_agent. Good compensation for 0% schema coverage.

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 clearly states 'Fetch the full event log for a completed run in chronological order' with specific verb and resource. It elaborates on the types of events included, distinguishing it from get_run_status.

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?

Implicitly indicates usage for completed runs, contrasting with status tools. No explicit when-not or alternative names, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools