Skip to main content
Glama

List the filings submitted by a company to its registry

list_filings
Read-onlyIdempotent

Retrieve a company's filing history sorted newest-first, with optional filtering by category and pagination. Use jurisdiction and company_id to get filings; pass back cursor or offset for additional pages.

Instructions

Return a company's filing history. Each filing has a filing_id, filing_date, category, description, and (when upstream exposes one) a document_id that round-trips to get_document_metadata / fetch_document. Raw upstream fields come through verbatim under jurisdiction_data. Results are newest-first.

Use the optional category parameter to filter. Common normalized categories: 'accounts', 'annual-return', 'capital', 'charges', 'confirmation-statement', 'incorporation', 'insolvency', 'liquidation', 'mortgage', 'officers', 'persons-with-significant-control', 'resolution'. Some jurisdictions also accept native form codes directly — pass the upstream code through unchanged if you have one.

Pagination: limit (default 25, max 1000). Some adapters use cursor pagination — pass back next_cursor as cursor to continue. Others use numeric offset. has_document flags whether the body can actually be retrieved via fetch_document; some registries expose only the metadata listing with the body paywalled or unavailable.

Not every registry publishes a filing list; unsupported jurisdictions return 501. Per-country caveats (ID format, accepted category values, cursor vs offset, document availability and pricing, paid-tier gates) — call list_jurisdictions({jurisdiction:"<code>"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionYesISO 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>'})`.
company_idYesRegistry-specific company ID. IE accepts an optional '/B' suffix for the business-name register.
categoryNoOptional filter on standardized category. GB: native Companies House category strings. IE: 'accounts'|'annual-return'|'capital'|'charges'|'incorporation'|'insolvency'|'officers'|'prospectus'|'registered-office'|'resolution'. IM: 'annual-return'|'articles'|'memorandum'|'incorporation'|'name-change'|'officers'|'resolution'|'charges' (mapped to upstream AR/AA/MA/INC/CCN/9N/RES/CRS; pass the raw upstream code directly for any other IoM document type). IS: 'annual-return'|'incorporation'|'articles'|'supplementary-notice'|'other', or the Icelandic column names ('Stofngögn'/'Samþykktir'/'Aukatilkynningar'/'Önnur gögn'), or the raw numeric typeid (1/4/5/6/7).
limitNoItems per page. Default 25.
offsetNoIE only. Skip the first N filings (pagination). Combine with limit.
cursorNoGB only. Opaque pagination cursor returned by a previous call as 'next_cursor'. Omit for the first page.
freshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
itemsNo
total_countNo
next_cursorNo
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, making the tool's non-destructive, idempotent, and schema-varying nature clear. The description adds context about raw upstream fields under jurisdiction_data, pagination details, and document availability, which are beyond annotations but do not contradict them. There is no contradiction.

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 paragraphs for purpose, filtering, pagination, and caveats. It is front-loaded with the core purpose and immediately useful details. Slightly verbose with per-country category examples inline, but all information is relevant and not redundant with schema.

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?

The description fully covers the tool's complexity: it explains expected output fields, pagination mechanisms, category usage across jurisdictions, error cases (501), and document availability. The output schema might exist but is not provided; however, the description sufficiently describes what is returned. All critical behaviors are documented.

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 86%, with categories providing detailed country-specific values and formats (e.g., GB, IE, IM, IS). The description adds clarification on category normalization and native code acceptance, and explains pagination (cursor/offset) beyond schema min/max. It adds meaning beyond schema for the fresh parameter (though brief) and jurisdiction (directing to list_jurisdictions).

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 starts with a clear, specific verb ('Return') and resource ('a company's filing history'), immediately stating the action and object. It details what each filing contains (filing_id, etc.) and differentiates the tool from siblings like get_company_profile or fetch_document by listing related document retrieval tools. The focus on filing history and round-tripping document IDs clearly distinguishes it.

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?

The description explicitly tells when to use this tool ('Return a company's filing history') and provides extensive guidance on filtering with category, pagination methods (cursor vs offset), and the has_document flag for document availability. It also warns of unsupported jurisdictions (501 error) and directs to list_jurisdictions for per-country caveats, giving clear when-not-to-use and alternative instructions.

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

Install Server

Other Tools

Latest Blog Posts

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