Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_seal_grant

Seal the exact scopes an agent was granted at connect time into a verifiable record, so out-of-scope use or quiet renewal scope expansion can later be detected and recomputed by anyone.

Instructions

Seal the exact scope granted at connect time, as presented by the principal-side connect flow: granted scope set, connector identity, agent identity, and the integration class (F = grant seal + runtime use capture; G = grant seal only). One metered op per grant seal. Grantseal seals the exact permissions an agent or app was granted at connect time, and the permissions it actually exercised as captured in your own agent runtime. If it used a scope it was never granted — or a renewal quietly added scopes — the sealed record names them, and anyone can recompute the verdict from the record itself.

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": {
      "connector_id": "<connector_id>",
      "agent_id": "<agent_id>",
      "granted_scopes": "<granted_scopes>",
      "integration_class": "<integration_class>"
    },
    "name": "grantseal_seal_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
connector_idYes
granted_scopesYes
connect_timestampNo
integration_classYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 two useful traits: sealing is metered ("One metered op per grant seal") and the resulting record is tamper-evident and independently recomputable. It does not state required permissions, whether re-sealing an already-sealed grant is allowed, idempotency, or failure behavior, which are significant gaps for a mutation tool with zero annotation coverage.

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

Conciseness3/5

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

The core instruction is front-loaded, but the second sentence largely restates the first ("seals the exact permissions an agent or app was granted at connect time"), and the closing verdict language is promotional rather than operational. Several clauses could be cut without losing information an agent needs to invoke the tool.

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

Completeness2/5

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

For a 5-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description should cover preconditions and return shape. It hints that a sealed record is produced but never says what the tool returns (seal ID, record body, verdict), and it omits permissions, retry, and duplicate-seal behavior entirely.

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 0%, so the description must compensate. It does add real meaning for the integration_class enum (F = grant seal + runtime use capture; G = grant seal only) and names the scope/identity inputs, but it says nothing about connect_timestamp or the expected format of granted_scopes, leaving one of five parameters entirely unexplained.

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 uses a specific verb+resource ("Seal the exact scope granted at connect time") and enumerates exactly what goes into the seal: granted scope set, connector identity, agent identity, and integration class. It also distinguishes the two integration classes, F and G. It falls short of a 5 because it never contrasts itself with the sibling grantseal_seal_renewal or grantseal_capture_use, and the second sentence drifts into describing runtime use capture, which muddies the boundary with those siblings.

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?

Usage is implied by the phrase "as presented by the principal-side connect flow" and "at connect time", which tells an agent this is the connect-time step. However, there is no explicit when-to-use/when-not guidance, no prerequisite statement, and no reference to the renewal or capture alternatives a caller might confuse this with.

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