tk-mcp

tk_coverage

Read-onlyIdempotent

Declare the connector's coverage, sourcing, and known gaps before concluding a Constitutional Tribunal search returned no results; each gap points to an alternate source.

Instructions

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the Constitutional Tribunal record "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the TK record. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tk_coverage"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`status`	No		ok
`families`	No
`as_of_note`	Yes	States what the dates mean, and what they do not promise.
`known_gaps`	No	Never empty. An empty list would mean 'not checked', not 'no gaps'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: every gap carries a fallback saying where to look instead, and the result always includes a non-empty list of known gaps — semantics an agent cannot infer from the annotations alone.

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?

Structure is front-loaded: the imperative purpose first, then the usage condition, then the return summary. It is slightly longer than strictly necessary because the gap rationale is stated twice in adjacent sentences, but every element is relevant and there is no filler.

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 an output schema present, the description is not obligated to explain return values, yet it still names the Coverage payload, its families, as-of note, and non-empty gap list. Combined with the rich annotations and explicit call conditions, an agent has everything needed to invoke this correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless invocation and spends no space on non-existent inputs.

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 opens with a specific verb and resource: 'Declare what this connector covers, how it is sourced, and what it does NOT cover.' That is unmistakably distinct from the sibling read tools (search_judgments, get_judgment_text), which fetch records rather than declare coverage metadata.

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 gives explicit trigger conditions: call before asserting the TK record 'does not contain' something, and whenever a search returns empty. It also explains why — an empty result may be a connector gap rather than a record gap — which directly routes the agent away from over-claiming based on sibling search results.

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

Deploy Server