The Chancery Lane Project

get_legal_resource

Read-only

Get one law, regulation, standard, framework or guidance, and the TCLP content citing it.

Versions are not tracked yet, so every citation has `staleness: "unpinned"`:
the content cites the instrument without naming a version. There is no
description yet; do not supply one from your own knowledge, and do not state
the instrument's legal effect.

Args:
    work_id: The instrument's `work_id`, from `find_legal_resources` or from a
        search result's "references".
    citing_limit: Maximum citing content items to return (1–100, default 20).

Returns:
    JSON with "resource", "citing" (each with id, title, url, content_type,
    edge, staleness) and "citing_total". `edge` (governs, references,
    describes) says how the content relates to the instrument; it is not a
    statement of the instrument's legal effect.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`work_id`	Yes
`citing_limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`citing`	Yes
`resource`	Yes
`citing_total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 6, 2026
- addedInput schema / properties / citing_limit / maximum
```
Added value: +100
```
- addedInput schema / properties / citing_limit / minimum
```
Added value: +1
```
- addedInput schema / properties / work_id / maxLength
```
Added value: +500
```
- addedInput schema / properties / work_id / minLength
```
Added value: +1
```
AddedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover only the safety profile (readOnly, non-destructive, openWorld), yet the description adds substantial behavioral context: versions are untracked so every citation carries staleness 'unpinned', there is no description field and the agent must not fabricate one, and the agent must not assert legal effect. It also explains the 'edge' relation semantics, which is exactly the kind of context annotations cannot supply.

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?

Front-loaded with purpose, then caveats, then explicit Args and Returns sections. Despite its length, every sentence conveys a distinct constraint (staleness, no-fabrication rule, no-legal-effect rule, edge semantics) rather than padding.

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?

Although an output schema exists and returns need not be described, the description still enumerates the return keys (resource, citing, citing_total, edge, staleness) and flags the staleness caveat an agent would otherwise misread. For a read-only lookup with two parameters, nothing material 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?

Schema description coverage is 0%, so the description carries the burden and does so well: it explains that work_id is the instrument's identifier sourced from find_legal_resources or a search result's references, and that citing_limit caps citing items (1–100, default 20). It does not restate the maxLength constraint, but the semantics added are meaningful.

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?

States a specific verb and resource: 'Get one law, regulation, standard, framework or guidance, and the TCLP content citing it.' It also clarifies the secondary payload (citing content), which cleanly distinguishes it from the plural sibling find_legal_resources.

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 routes the agent by stating where work_id comes from — 'from find_legal_resources or from a search result's "references"' — which implicitly tells the agent this is a follow-up lookup rather than a search entry point. It stops short of an explicit when-not statement, so it is clear context without full exclusion guidance.

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

All The Chancery Lane Project tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?