Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_check

Returns a counterparty verdict for a grant seal, showing the verdict class and only the names of out-of-scope or added scopes.

Instructions

Counterparty view: the verdict class and the names of out-of-scope or added scopes only. 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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
grant_seal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. It adds useful behavioral context by stating 'Unmetered' and limiting the returned data to verdict class and out-of-scope or added scope names, but it does not confirm read-only behavior, side effects, auth requirements, or error handling.

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?

The description is two terse sentences with no wasted words, and 'Unmetered.' is efficiently front-loaded as a practical constraint. However, the fragmented colon style and absence of an explicit verb make it slightly cryptic rather than fully clear.

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?

With no annotations and no output schema, the description should more fully explain the input and return semantics. It partially covers return scope and cost, but omits grant_seal_id meaning, usage context, and sibling differentiation, leaving an agent with gaps 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?

There is one required parameter, grant_seal_id, with 0% schema description coverage. The description never mentions the parameter or explains what value it should contain, so only the parameter name supplies meaning and the description adds nothing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a 'Counterparty view' and the returned fields ('verdict class' and out-of-scope or added scope names), but it never states the operation explicitly. An agent can infer a check from the tool name, yet the description does not distinguish this from the sibling grantseal_get_verdict.

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 when-to-use guidance, no exclusions, and no named alternative. 'Counterparty view' hints at a context, but it does not explain when to call this instead of grantseal_get_verdict or what prerequisites exist.

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