Skip to main content
Glama
Sign In

KeyHalve - verify sealed documents

by com.keyhalve
OverviewDiscussionsAdmin

keyhalve_status

Read-only

Live status of a KeyHalve-sealed document by id: active, revoked (with reason/time), or outside its validity window. Lighter than keyhalve_verify — status only, no integrity or rail checks. Use for "is this still good right now?"

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": {
      "document_id": "<document_id>"
    },
    "name": "keyhalve_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesThe document id, e.g. vp_…, kh_…, cb_….

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's additional 'status only, no integrity or rail checks' provides useful context about what the tool does NOT do, going beyond the annotations. It also clarifies that it reports 'outside its validity window' as a status. Non contradicting and adds value, though it doesn't detail response format or error behavior.

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?

The description is two sentences, front-loaded with the core function, and every clause is informative. It includes the status outcomes, the sibling comparison, and usage guidance without redundancy.

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

Completeness4/5

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

With no output schema, the description partially covers return values by listing possible statuses (active, revoked, outside validity window) and even includes reason/time for revoked. For a simple status tool with one param, this is reasonably complete, though it doesn't specify exact response structure or error handling.

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 description coverage is 100% for the single parameter, and the schema already explains the document_id format with examples. The description just says 'by id' without adding further semantic detail, so it doesn't elevate beyond the baseline.

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 starts with 'Live status of a KeyHalve-sealed document by id' which specifies the verb (status check), resource (document), and scope (live status with three outcome categories). It explicitly contrasts with keyhalve_verify, noting this tool is 'lighter' and does not perform integrity or rail checks, clearly distinguishing it from siblings.

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

Usage Guidelines5/5

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

It directly states when to use this tool: 'Use for "is this still good right now?"' and differentiates from keyhalve_verify by saying it's status-only vs. full verification. This gives explicit usage context and an implicit alternative, which is strong guidance.

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

All KeyHalve - verify sealed documents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources