Skip to main content
Glama
Sign In
Gulliver

Gulliver

by laaielichter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

gulliver_receipt

Read-onlyIdempotent

Retrieve proof of an earlier preflight, rehearsal, run, diff, or check: SQL, estimates, measured numbers, budget verdict, and approvals. Use it after a run to explain what happened or why.

Instructions

Get the receipt (proof) of an earlier preflight, rehearsal, run, diff or check: the SQL, estimates, measured numbers, budget verdict and any human approval. Markdown is for showing a human or pasting into a PR; json is for agents. Reads the local receipt log only. Use it after a run when the human asks what happened or why.

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown for humans, json for agents.markdown
receipt_idNoThe receipt_id field from an earlier preflight, rehearse, run, diff or check result, or 'latest' for the newest. An unknown id returns status error.latest

Output Schema

NameRequiredDescriptionDefault
statusYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / properties / format / description
      Previous value: -"Output format."New value: +"markdown for humans, json for agents."
    • changedInput schema / properties / receipt_id / description
      Previous value: -"receipt_id from an earlier result, or 'latest'."New value: +"The receipt_id field from an earlier preflight, rehearse, run, diff or check result, or 'latest' for the newest. An unknown id returns status error."
  2. Changed3 schema fields changedv0.1.1
    • addedOutput schema / properties
      Added value: +{
+  "next_step": {
+    "type": "string"
+  },
+  "status": {
+    "enum": [
+      "ok",
+      "warn",
+      "block",
+      "needs_rehearsal",
+      "needs_approval",
+      "skipped",
+      "fail",
+      "error"
+    ],
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "status",
+  "next_step"
+]
    • changedOutput schema / title
      Previous value: -"gulliver_receiptDictOutput"New value: +"GulliverResult"
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description reinforces the scope with 'reads the local receipt log only', which rules out live execution or remote state. It also implicitly characterizes the payload (estimates, budget verdict, approvals) beyond the safety profile, though it says nothing about retention or how far back receipts go.

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?

Three tight sentences, front-loaded with the object of the call before the audience/format note and the trigger. Dense but every clause carries information; the middle clause about formats is the closest to redundancy given the schema already says the same.

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 two-parameter read tool with full schema coverage, an output schema and complete annotations, nothing an agent needs to select or invoke it is missing. The description covers what is retrievable, which sibling outputs produce receipts, and the appropriate call timing.

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 coverage is 100% and both parameters are already documented in the schema, including the enum values, the 'latest' default and the unknown-id error behavior. The description's format guidance largely restates the schema, adding no new syntax or edge-case detail, so 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?

Names a specific verb and resource (get the receipt) and immediately enumerates what the receipt contains: SQL, estimates, measured numbers, budget verdict, human approval. It also pins the receipt to outputs of named sibling tools (preflight, rehearse, run, diff, check), so an agent can place it precisely in the workflow.

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 a concrete trigger: use it after a run when the human asks what happened or why, plus format routing (markdown for humans/PRs, json for agents). It stops short of naming an alternative sibling for the same need or stating when not to call it, so it is clear context without explicit exclusions.

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