Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_get_verdict

Retrieve a grant seal’s full verdict record to inspect verdict status, out-of-scope and added scopes, taxonomy version, and receipt references for audit or renewal review.

Instructions

The full verdict record for a grant seal: verdict, use verdict facet, named out-of-scope and added scopes, taxonomy version, receipt refs. Class G records return GRANT-SEALED. 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_get_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_seal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden; it discloses the Class G special-case return value and that the call is unmetered, which are genuinely useful beyond structured data. It omits whether the operation is read-only, what happens when the seal ID is unknown or invalid, and whether verdicts are volatile or cached across recomputes.

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?

It is short and front-loaded, with the record contents listed up front. However, the telegraphic fragment style ('verdict, use verdict facet, named out-of-scope and added scopes...') prioritizes brevity over clarity, and 'Unmetered' hangs as an unexplained trailing fragment.

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?

There is no output schema, but the field enumeration partially compensates by telling the agent what the response contains, and the Class G note covers one important return case. Still missing for a single-parameter lookup with zero annotation coverage: ID format/derivation, failure behavior, and routing against siblings like grantseal_check.

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% for the single required parameter, so the description must compensate and does not. It adds nothing about grant_seal_id's format, where an agent obtains one, or whether it is a seal handle versus a receipt reference.

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 names a specific resource — the full verdict record for a grant seal — and enumerates its contents (verdict, use verdict facet, out-of-scope and added scopes, taxonomy version, receipt refs). The retrieval verb is only implicit in the noun phrase, and no sibling tool is named for contrast, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus grantseal_check or the seal tools, and no prerequisites or exclusions. The only usage-adjacent information is the special case that Class G records return GRANT-SEALED, which describes an outcome rather than when to select this tool.

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