Skip to main content
Glama
Sign In
Gulliver

Gulliver

by laaielichter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

gulliver_status

Read-onlyIdempotent

Lists configured database connections, their engines and access modes, plus per-agent budget limits and today's spend; call it first to get a connection name for other tools.

Instructions

Show the configured connections (name, engine, read-only or writable), the budget limits and the money spent today, per agent. Call this first in a session: other tools take a connection name from this list. Reads local config and the spend ledger only; never queries a database. For table sizes use gulliver_inspect instead.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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_statusDictOutput"New value: +"GulliverResult"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real context beyond them: it reads only local config and the spend ledger and never queries a database, which tells the agent there is no connection latency or live state. It stops short of describing freshness or output shape, but the output schema covers the latter.

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?

Four short sentences, each doing distinct work: payload contents, session ordering, data-source scope, and alternative routing. The most important instruction (call first) is front-loaded in the second sentence with no 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?

With zero parameters, an output schema, and rich annotations, the description supplies exactly the missing pieces: what is returned, when to call it, what it does not touch, and where to go instead. Nothing needed to invoke it correctly is absent.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit.

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 a fully enumerated resource set: connections (name, engine, read-only or writable), budget limits, and money spent today per agent. It also names a sibling it is not (gulliver_inspect), so an agent can distinguish it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit ordering instruction ('Call this first in a session') with the reason (other tools take a connection name from this list), and an explicit exclusion routing table-size questions to gulliver_inspect. Both when-to-use and when-not-to-use are covered.

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