Skip to main content
Glama

Record AutoPilot ledger event

autopilot_record_event

Write one sanitized AutoPilot proof event to the tenant ledger. Use it to record claim, check, merge, close, proof, and blocker receipts before claiming zero-touch proof.

Instructions

Writes one sanitized AutoPilot proof event to the tenant ledger. Use this for claim, check, merge, close, proof, and blocker receipts before claiming zero-touch proof.

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": {
      "event_type": "<event_type>",
      "actor_agent_id": "<actor_agent_id>",
      "ref_kind": "<ref_kind>",
      "ref_id": "<ref_id>"
    },
    "name": "autopilot_record_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
ref_idYesStable object id, such as a PR number, todo UUID, dispatch id, or run id.
payloadNoNon-secret proof details. Secret-looking keys or values are rejected by the API.
ref_kindYesStable object type this event proves.
event_typeYesTyped ledger event. Use proof_result for check results and todo_state_change for close.
actor_agent_idYesAutomation seat or App identity that performed the action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool is a non-readonly, non-idempotent write. The description adds useful context by noting that events are sanitized and scoped to a tenant ledger, and that it records one event per call. However, it does not explain retry behavior, duplicate handling, or error conditions—important for a non-idempotent ledger write.

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?

The definition is two sentences and front-loads the core action and scope. Every sentence is relevant, with no filler or repetition.

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?

For a five-parameter write tool with a fully documented schema and annotations covering safety and idempotency, the description gives enough context to call it correctly: what it writes, where, what receipt types to use, and the broader zero-touch proof workflow. It stops short of describing return values or duplicate-event behavior, but no output schema exists and the annotations reduce the burden.

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 the schema already documents all five parameters, enums, and payload restrictions. The description lists example receipt types but adds no syntax, formatting, or mapping details beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 specific verb and resource: writes one sanitized AutoPilot proof event to the tenant ledger. It implies a relationship to zero-touch proof and the sibling autopilot_zero_touch_metrics, but does not explicitly name or contrast with any sibling tool.

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?

The description gives clear usage context: use it for claim, check, merge, close, proof, and blocker receipts, and specifically before claiming zero-touch proof. It does not explicitly state when not to use it or name an alternative tool.

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