Skip to main content
Glama
Cyan Eclipse Grantseal

Cyan Eclipse Grantseal

Official

grantseal_recompute

Recompute a verdict from exported grant captures and a taxonomy version without service state, enabling validation of scope decisions from stored evidence.

Instructions

Recompute a verdict from the exported captures plus the taxonomy version, with no service state. 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_capture": "<grant_capture>",
      "taxonomy_version": "<taxonomy_version>"
    },
    "name": "grantseal_recompute"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_captureNo
grant_captureYes
taxonomy_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry some of the behavioral burden: it discloses that the computation is stateless relative to the service and that it is unmetered, which matters for cost and offline use. It does not address determinism, whether captures must be unmodified, or what happens with an unknown taxonomy_version — all relevant for a recompute tool.

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?

Two tight sentences with the core action front-loaded; "Unmetered" as a trailing fragment is terse but informative rather than wasteful. Nothing could be cut without losing a signal.

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 three-parameter tool with nested objects, no annotations, and no output schema, the description leaves key gaps: the role of use_capture, the expected capture provenance, and the form of the returned verdict. It is underspecified relative to the tool's complexity.

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% with three parameters and nested objects. The description only implicitly maps "exported captures" to grant_capture and "taxonomy version" to taxonomy_version; the third parameter use_capture is entirely unexplained, and the internal shape of the nested objects is undocumented in both places.

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 verb and output ("Recompute a verdict") plus the inputs it derives from (exported captures and taxonomy version), which distinguishes it from grantseal_get_verdict (retrieval) and grantseal_check. It stops short of naming the sibling it is the offline counterpart to, so differentiation is implied rather than explicit.

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?

"with no service state" implies this is the offline/air-gapped path, which is useful context for selecting it over service-backed siblings, but no explicit when-to-use, when-not-to-use, or named alternative is given. The agent must infer the selection rule.

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