Skip to main content
Glama

Kevros — Agentic Identity Trust

by io.github.ndl-systems

Verify Release Token

verify-token
Read-onlyIdempotent

Verify a release token from another agent. Confirms the token is authentic, was issued by the Kevros gateway, and remains currently authorized after any halt or mode transition. Free, no API key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
release_tokenYesRelease token string received from governance_verify
token_preimageNoDeprecated. The gateway now performs verification entirely server-side using the release_token alone; any value supplied here is ignored. Field retained for backward compatibility with v1 SDK callers and will be removed in a future release.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds behavioral detail about what verification checks (authenticity, issuer, current authorization) and the lack of an API key requirement, enhancing transparency beyond the annotation flags.

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?

Three sentences, purpose first, then verification scope, then cost/access. No redundant or extraneous content.

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

Completeness5/5

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

With schema covering parameters, annotations covering safety, and output schema present, the description adequately covers purpose and usage context for correct invocation. The mention of 'after any halt or mode transition' adds important contextual completeness.

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 descriptions fully document both parameters, including the deprecation and ignored behavior of token_preimage. The tool description does not add further parameter-level detail, so the baseline 3 applies given high schema coverage.

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

Purpose5/5

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

The description clearly states the tool verifies a release token from another agent, confirming authenticity, gateway issuance, and current authorization. This specific verb-resource combination distinguishes it from general tools like verify and verify-outcome.

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

Usage Guidelines4/5

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

Provides clear context on when to use: when a release token is received from another agent, especially after halt or mode transitions. It does not explicitly compare against sibling tools like verify or verify-outcome, so no exclusionary guidance.

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

All Kevros — Agentic Identity Trust toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct action or resource: attest creates provenance records, bind declares intent, bundle aggregates evidence, verify checks policy pre-execution, verify-outcome validates results, and verify-token authenticates release tokens. Even the verify-* family is clearly differentiated by timing and purpose.

Naming Consistency4/5

Tool names consistently use lowercase imperative verbs, with hyphenated modifiers for multi-word names (check-peer, verify-outcome, verify-token). The pattern is mostly consistent, though some tools are bare verbs (attest, bind, health) while others include a noun, creating a minor deviation from strict verb_noun style.

Tool Count5/5

Nine tools is well within the ideal range for this domain. Each tool serves a clear purpose in the agentic identity trust lifecycle, from evidence creation to verification and peer assessment, without redundancy or excessive sprawl.

Completeness4/5

The tool surface covers the core workflow: intent binding, policy verification, provenance attestation, outcome verification, token verification, and compliance bundling. Minor gaps exist such as missing explicit revocation or role management, but agents can complete the primary governance lifecycle.

Resources