Skip to main content
Glama

Lawstronaut

by com.lawstronaut

get_document_with_version

Read-onlyIdempotent

Retrieves a specific document with a specific version. Use this tool when: - The user wants to find a specific document with a specific version - The user asks about available a specific document with a specific version

Parameters:
- document_id (required): Document ID.
- version (required): Version.

Returns:
- Content with version with title, section_title, publication_date, effective_date, expiration_date, date_of_enactment, date_of_last_amendment, date_of_repealed, date_of_decision, status, version, source_identifier, source_secondary_identifier, issuing_authority, type_of_authority, language, legal_link, repealed, metadata, summary, tags, source_keywords, crawling_date, portal, portal_name, last_updated
- Only returns content that has crawled data with the specific version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionYesVersion
document_idYesDocument ID

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds a useful behavioral constraint: 'Only returns content that has crawled data with the specific version,' providing transparency beyond annotations.

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 well-structured with clear sections for function, usage, parameters, and returns. It is moderately concise, though the return field list is somewhat lengthy. Overall, it is front-loaded and informative.

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

Completeness4/5

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

Given no output schema, the description compensates by listing return fields and specifying the crawled data condition. It covers the tool's core functionality but could mention error handling or missing versions for full completeness.

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 schema already documents both parameters thoroughly. The description repeats parameter names and basic descriptions without adding meaningful extra semantics, meeting baseline expectations.

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 retrieves a specific document with a specific version, using a specific verb and resource. It effectively distinguishes from sibling tools like get_document_text or get_source_url by focusing on version retrieval.

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 includes a 'Use this tool when' section that clearly indicates the context (user wants a specific document with a specific version). However, it does not explicitly mention when not to use it or suggest alternatives, which would improve guidance.

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

All Lawstronaut toolsInspect
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

A3.7/5.0
Disambiguation4/5

Most tools have distinct purposes, but evidence_pull and get_document_text both return full text, which could cause confusion. Other tools like list_documents and get_markdown are clearly differentiated.

Naming Consistency3/5

Names follow a mix of 'list_', 'get_', and one-off names like 'evidence_pull' and 'horizon_scan'. The verb_noun pattern is present but inconsistent.

Tool Count4/5

16 tools is reasonable for a legal document retrieval server, though some functionality overlaps (e.g., multiple ways to get document text). Still well-scoped for the domain.

Completeness4/5

Covers browse, filter, and retrieve operations comprehensively. Missing a general text search tool, but horizon_scan offers a recent-changes scan. Minor gap.

Resources