Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_export_captures

Exports a grant's sealed captures, including receipt chain head and taxonomy version, so you can independently recompute and verify scope usage.

Instructions

Export the sealed captures for a grant (grant capture, latest use capture, renewal records) with the receipt chain head and taxonomy version, for independent recomputation. Unmetered.

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": {
      "grant_seal_id": "<grant_seal_id>"
    },
    "name": "grantseal_export_captures"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_seal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the payload composition (which captures and metadata are returned) plus the cost behavior ('Unmetered'). It omits permissions/auth requirements and the serialization format, which prevents a 5 for a mutation-free but security-relevant export.

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?

One dense sentence with the exported contents front-loaded and no filler; the trailing 'Unmetered.' is terse but earns its place as a cost signal. Slightly over-packed with parenthetical lists, but efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description usefully states what the export contains. It leaves the caller guessing about the parameter's meaning and the returned format, which is a meaningful gap given no output schema exists to fill it in.

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

Parameters2/5

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

The single parameter is grant_seal_id at 0% schema coverage, and the description only says 'for a grant', which is not the same concept as a seal ID. It adds no clarity on identifier form, source, or whether a seal handle versus grant identifier is expected.

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 opens with a specific verb and resource ('Export the sealed captures for a grant') and enumerates exactly what is included (grant capture, latest use capture, renewal records, receipt chain head, taxonomy version). That level of specificity separates it from siblings like grantseal_recompute or grantseal_get_verdict, though it never names an alternative outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'For independent recomputation' implies the reason to call this rather than a verdict or check tool, and 'Unmetered' signals cost is not a concern. There is no explicit when-to-use vs. when-not guidance or reference to a sibling by name, so the agent must infer the boundary.

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