Thor Henning Hetland — signed knowledge web

kcp_trace

Produce a decision trace for a task: every unit in the manifest annotated with the gate cascade it was evaluated through (audience, temporal, relevance, budget, context, etc.). Same inputs as kcp_plan; returns the canonical plan plus structured per-unit gate verdicts.

Input Schema

TableJSON Schema

Name	Required	Description
`env`	No	Runtime environment for federation context selection (dev/test/staging/prod)
`role`	No	Agent role for audience targeting (default: agent)
`task`	Yes	The task to plan knowledge loading for
`as_of`	No	ISO date for temporal evaluation (default: today, UTC)
`attest`	No	Attestation provider the agent can present, matched against the manifest's trusted_providers
`budget`	No	Spend ceiling for pay-per-request units
`follow`	No	Follow eligible federation refs (default false)
`strict`	No	Fail-closed: drop non-eligible units instead of listing them
`methods`	No	Payment methods the agent can settle, e.g. ["free","x402"] (default: free only)
`currency`	No	Budget currency (default USDC)
`manifest`	Yes	Path, directory, or HTTPS URL of a knowledge.yaml
`max_depth`	No	Federation hops to follow when follow=true (default 1)
`max_nodes`	No	Cap on total manifests fetched across the walk (default 64)
`max_units`	No	Cap on selected units (default 5)
`credentials`	No	Credential kinds the agent holds, e.g. ["mtls","api_key"] — opens access-gated units
`context_budget`	No	Token ceiling for what the plan loads into the caller's context window; over-budget units skipped with the arithmetic
`allow_private_hosts`	No	Permit fetches to loopback/private/link-local hosts and http:// (default false — fail-closed)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It states the output includes 'canonical plan plus structured per-unit gate verdicts', but does not disclose whether the tool mutates state, requires special permissions, or has rate limits. The read-only nature is implied by 'trace' but not explicit.

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 efficient sentences: the first defines the core action and output, the second clarifies the relationship to a sibling tool. Every word earns its place with no redundancy.

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

Completeness3/5

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

Given the tool has 17 parameters (2 required) and no output schema, the description does not fully compensate. It describes the high-level output but omits details on return structure, error conditions, or performance characteristics. A more complete description would mention the format of verdicts or potential side effects.

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%, so the parameters are fully documented in the schema. The description adds that the inputs are the same as kcp_plan, but does not provide additional semantic meaning beyond what the schema already offers. Baseline 3 is appropriate.

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 produces a decision trace for a task, annotating each unit with gate cascade verdicts. It uses a specific verb ('Produce') and resource ('decision trace'), and the mention of 'same inputs as kcp_plan' distinguishes it from sibling tools like kcp_plan which would produce just the plan.

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?

The description explicitly says 'Same inputs as kcp_plan' and notes it returns additional structured verdicts, which implies using this tool over kcp_plan when a trace is needed. However, it does not explicitly state when not to use this tool or provide alternatives beyond the sibling names.

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

All Thor Henning Hetland — signed knowledge web tools Inspect

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 has a clearly distinct purpose: load retrieves content, plan generates a plan, replay cross-examines a plan, trace produces a decision trace, and validate lints the YAML. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent 'kcp_verb' pattern (load, plan, replay, trace, validate), making them predictable and easy to distinguish.

Tool Count5/5

5 tools is well-scoped for the specialized domain of knowledge web planning. Each tool addresses a specific need without excess or deficiency.

Completeness4/5

The tool set covers the core workflow: planning, loading, validating, and analyzing plans. A potential minor gap is the lack of a tool to modify the knowledge configuration or list available units, but the existing surface is sufficient for its intended use.

Resources

Need Help?