Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_seal_renewal

Seal a renewed or reconnected grant and compare it with the original seal at presentation, flagging added scopes as EXPANDED-AT-RENEWAL or marking no change without metering renewals.

Instructions

Seal a renewal or re-connect grant and diff it against the original seal at presentation: added scopes verdict EXPANDED-AT-RENEWAL naming them; a renewal that changes nothing records a no-change marker. Renewals do not meter.

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>",
      "renewed_scopes": "<renewed_scopes>"
    },
    "name": "grantseal_seal_renewal"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_seal_idYes
renewed_scopesYes
renewal_timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 does disclose real post-state semantics: an added-scope diff yields an EXPANDED-AT-RENEWAL verdict naming the scopes, a no-change renewal records a marker, and renewals do not meter. It stops short of saying whether sealing is an immutable write, whether it is idempotent, or what it returns.

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?

Two tight sentences, purpose front-loaded, with the verdict and no-metering facts packed into a compact clause. No filler; the density is warranted by the domain vocabulary.

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?

A three-parameter tool with no annotations and no output schema needs coverage of mutation semantics and parameter formats; the description delivers the verdict/marker behavior but leaves the write contract and all three argument shapes unexplained. Adequate for selection, thin for correct invocation.

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?

Schema description coverage is 0%, so the description must compensate for all three parameters, and it largely doesn't: grant_seal_id and renewal_timestamp are never addressed, and only 'added scopes' loosely glosses renewed_scopes. Format, timestamp expected values, and ID semantics remain undocumented everywhere.

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?

States a specific verb and resource ('Seal a renewal or re-connect grant') and adds the distinctive behavior — diffing against the original seal at presentation. That differentiates it from grantseal_seal_grant well enough, though the term 'seal' itself is never unpacked.

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 'renewal or re-connect grant' rather than stated: an agent can infer this is the renewal path, but there is no explicit instruction on when to prefer it over seal_grant, nor any prerequisite or exclusion. No sibling is named or routed away from.

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