Skip to main content
Glama

get_markdown

Read-onlyIdempotent

Retrieves markdown for a specific jurisdiction and optional filters. Use this tool when: - The user asks about available markdown for a portal name, title, section_title, url, status, repealed, publication_date and crawling_date - The user wants to filter markdown for type of authority, issuing authority, source identifier, source secondary identifier, tag

Parameters: 
- iso (required): Jurisdiction ISO code (e.g. "US").
- portal (optional): Portal name.
- limit (optional): Number of results to return.
- offset (optional): Number of results to skip.
- document_id (optional): Document ID.
- title (optional): Title.
- section_title (optional): Section title.
- url (optional): URL.
- last_updated (optional): Last updated date.

Returns:
- Content markdown list with document_id, content_markdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoYesFilter by Jurisdiction ISO code (e.g. 'US')
tagNoFilter by tag
urlNoFilter by URL
langNoFilter by language
limitNoNumber of results to return
titleNoFilter by title
offsetNoNumber of results to skip
portalNoFilter by portal name
statusNoFilter by status
versionNoFilter by version
repealedNoFilter by repealed status
document_idNoFilter by document ID
last_updatedNoFilter by last updated date
crawling_dateNoFilter by crawling date
section_titleNoFilter by section title
effective_dateNoFilter by effective date
file_data_onlyNoReturn file data only
last_amendmentNoFilter by last amendment date
expiration_dateNoFilter by expiration date
date_of_decisionNoFilter by date of decision
publication_dateNoFilter by publication date
date_of_enactmentNoFilter by date of enactment
issuing_authorityNoFilter by issuing authority
source_identifierNoFilter by source identifier
type_of_authorityNoFilter by type of authority
source_secondary_identifierNoFilter by secondary source identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety coverage is handled by annotations. The description adds a useful return contract ('Content markdown list with document_id, content_markdown'), but it does not disclose pagination behavior or how multiple filters interact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool purpose is front-loaded and the use-case bullets make the structure readable. However, the Parameters section duplicates schema information, is incomplete, and the description includes both usage filters and a parameter list that overlap without being aligned.

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?

For a 26-parameter retrieval tool with no output schema, the description provides the required iso field and a basic return shape, which is helpful. Yet it omits many available filters from its parameter list, does not describe pagination or default behavior, and offers no detail on how filters combine, leaving notable gaps for a tool this complex.

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 every parameter; the description mostly repeats labels rather than adding deeper meaning. Its Parameters section is also incomplete relative to the 26-property schema, leaving some filterable fields like status, tag, and repealed out of the listed parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: retrieving markdown for a jurisdiction, with optional filters, and it is more than a restatement of the tool name. However, it does not explicitly differentiate from siblings like get_document_text or get_document_with_version.

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 when to use the tool via 'Use this tool when...' bullets, listing several filter categories such as title, status, repealed, issuing_authority, and tag. It lacks when-not guidance or alternative tool routing, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.