openregistry

Open the navigation index for a cached document

get_document_navigation

Read-onlyIdempotent

Get structural outline and text previews of large PDFs to locate key sections like balance sheets before fetching full pages. Returns bookmarks, per-page summaries, keyword landmarks, and source URLs. Always follow up with fetch_document_pages for authoritative content.

Instructions

For PDFs that don't fit in a single document block (>~20 MB or >100 pages) OR whenever you need to locate specific sections, call this FIRST before fetching content. Returns outline (PDF bookmarks), per-page text previews (first ~200 chars), keyword-matched landmarks (balance sheet, directors report, auditor report etc.), text_layer classification, and source URLs.

CRITICAL — these are NAVIGATION AIDS ONLY. Page previews, outline titles, landmark matches, and search snippets may be truncated, contain OCR errors, or match false positives. NEVER cite them as source material for numbers, quotes, legal text, financial figures, dates, or names. Always follow up with fetch_document_pages(pages=) to retrieve authoritative content before answering.

Requires the document bytes to already be cached — call fetch_document once first if this is a new document.

Input Schema

TableJSON Schema

Name	Required	Description
`jurisdiction`	Yes	ISO 3166-1 alpha-2 country code (uppercase). All registries are official government sources. Currently supported: AU, BE, CA, CA-BC, CA-NT, CH, CY, CZ, DE, ES, FI, FR, GB, HK, IE, IM, IS, IT, KR, KY, LI, MC, MX, MY, NL, NO, NZ, PL, RU, TW. Per-country capability, ID format, examples, status mapping, and caveats: call `list_jurisdictions({jurisdiction:'<code>'})`. To find which countries support a specific tool: `list_jurisdictions({supports_tool:'<tool>'})`.
`document_id`	Yes
`fresh`	No	Set true to ignore the cached index.json and re-run pdfjs against the stored source bytes. Does not re-pull from upstream.
`company_id`	No	OVERRIDE (rare use). Normally auto-resolved from the list_filings side-cache.
`transaction_id`	No	OVERRIDE (rare use). Normally auto-resolved.

Output Schema

TableJSON Schema

Name	Required	Description
`queried_at`	Yes	ISO-8601 + Europe/London timezone stamp for when the registry was queried.
`jurisdiction`	No
`document_id`	No
`pages`	No
`headings`	No
`outline`	No

Tool Definition Quality

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds critical context: results are navigation aids only, may contain truncations and errors, and should never be cited as source material. It also requires document to be cached first.

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?

Well-structured with clear sections and warnings. The critical usage note is front-loaded. Could be slightly more concise by removing redundancy in the warning, but overall effective.

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?

Given the output schema exists, the description covers the purpose, prerequisites, limitations, and post-usage steps comprehensively. No gaps for a navigation index tool.

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 coverage is 80%, with most parameters already described. The description adds no further param details beyond the schema, but the schema itself is relatively clear. No additional semantics are needed for the core parameters.

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 opens a navigation index for cached documents, specifying it returns outline, page previews, landmarks, and classification. It distinguishes itself well from siblings like fetch_document_pages by being the first-call for navigation.

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?

Explicitly states when to use ('call this FIRST before fetching content' for large PDFs or locating sections) and when not to cite results, with clear instructions to follow up with fetch_document_pages for authoritative content.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sophymarine/openregistry'

If you have feedback or need assistance with the MCP directory API, please join our Discord server