TWZRD Agent Intelligence

get_claim

Read-onlyIdempotent

Read the Vuori Kore Short listing-claim artifact (com.twzrd.shopping.listing_claims/1.1).

Tool twin of the twzrd://claims/vuori-kore resource: what is claimed about this
checkout, by whom, in what state, on what evidence. Verified on every read
(publication signature, artifact digest, schema, evidence binding); a read that
fails any check is refused, never served. `unknown` claims stay unknown. Each claim
carries expires_at; after it, treat the claim as historical. Read-only; this never
starts a payment or checkout.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`uri`	Yes	The MCP resource this tool mirrors.
`text`	Yes	The artifact or evidence bundle, byte-for-byte as the resource serves it. Parse it after checking `digest`.
`digest`	Yes	sha256 of the exact bytes in `json`, as bound in the signed publication.
`artifact_id`	Yes	Artifact id of the signed publication that was read.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses detailed verification behavior: publication signature, artifact digest, schema, evidence binding, and that a failing read is refused. It also notes that unknown claims stay unknown and that claims carry an expiry. This exceeds the annotation coverage significantly.

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 compact and front-loaded with the core purpose, then adds verification, state behavior, and safety. Each sentence contributes new information; there is no filler or repetition. It is slightly long but appropriate for the complexity of the resource.

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?

For a zero-parameter read tool with an output schema, the description fully covers what the tool does, its safety profile, edge cases (unknown, expired), and verification guarantees. Nothing an agent needs to decide whether to call it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description need not explain any. The schema is trivially covered at 100%. Per calibration, a baseline of 4 applies, and the description adds no parameter-related confusion.

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 identifies the specific artifact (Vuori Kore Short listing-claim), states the resource it twins, and enumerates the information it provides (what is claimed, by whom, state, evidence). It also distinguishes its read-only nature from any payment/checkout actions, making its purpose unambiguous among sibling tools.

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?

It explicitly states the tool is read-only and never starts a payment or checkout, which is a clear usage constraint. It also explains that unknown claims remain unknown and that after expires_at the claim is historical, providing context on when to rely on the result. However, it does not name alternative tools for comparison, so it lacks explicit exclusion guidance.

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

All TWZRD Agent Intelligence tools Inspect

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.