A tenant’s full sealed-claim stream, newest first. Matured claims include their text and salt. Optional limit up to 200
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| tenant | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | ||
| tenant | Yes | ||
| records | Yes |
Changes observed during successful MCP inspections.
Input schema / x-lexicon / bundleSha256Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"Input schema / x-lexicon / bundleSha256Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"Input schema / x-lexicon / bundleSha256Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"Input schema / x-aliasesAdded value: +{
+ "limit": [
+ "Limit",
+ "limits",
+ "$limit",
+ "_limit",
+ "Limits"
+ ]
+}Input schema / x-lexiconAdded value: +{
+ "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+ "name": "ChainHelix Agentic Lexicon",
+ "resolve": "lexicon_resolve",
+ "spec": "lexicon_spec",
+ "version": "0.1.0"
+}Input schema / x-vocabAdded value: +{
+ "limit": "data.limit",
+ "tenant": "agent.tenant"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the disclosure burden, and it reveals useful behavior: results are newest first, matured claims include text and salt, and limit caps at 200. It does not cover authentication or error behavior, but for a read-only listing tool the disclosed details are substantive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Every sentence earns its place: scope, ordering/content, and limit. It is brief, front-loaded, and contains no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given only two flat parameters and an available output schema, the description covers the caller's main needs: which tenant, optional cap, ordering, and what appears once claims mature. It lacks sibling-routing context, but that is already penalized in usage_guidelines and does not block correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It adds meaning to limit (optional, up to 200) and ties tenant to the stream, but it does not explain tenant ID format, default limit, or how the limit interacts with the full stream.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description names a specific verb and resource: a tenant's full sealed-claim stream, ordered newest first. It is clear and distinct from stats/status siblings, but it does not explicitly compare itself to any sibling, so it stops short of full differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to choose this tool over siblings such as attestation_stats, attest_status, or attest. The only practical hint is the optional 200-item limit, which is a parameter note rather than a usage rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.