Skip to main content
Glama
Sign In

Fara

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Registrant Documents

get_registrant_documents
Read-onlyIdempotent

List FARA filings (PDF documents) for a registrant by registration_number (from search_registrants) — registration statements, supplemental statements, informational materials, exhibits, etc. Each row links the document to the specific foreign principal/country it concerns and gives a direct PDF URL. Optionally filter CLIENT-SIDE by document_type or country substring. Results are capped. Keyless.

Input Schema

NameRequiredDescriptionDefault
limitNoMax documents to return (default 50, hard cap 100).
countryNoOptional case-insensitive substring filter on the associated foreign-principal country.
document_typeNoOptional case-insensitive substring filter on document type, e.g. "supplemental", "exhibit", "informational".
registration_numberYesFARA registration number of the registrant (from search_registrants).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "registration_number": 5645
+  },
+  {
+    "country": "uae",
+    "document_type": "supplemental",
+    "limit": 20,
+    "registration_number": 5645
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, open-world, idempotent, and non-destructive. The description adds that results are capped, filters are client-side, and each row includes foreign principal details and a PDF URL, which are useful behavioral details 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 two sentences, front-loads the main action, and is generally concise. The term 'Keyless' is somewhat cryptic and could be clearer, but overall it is efficiently structured.

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 the schema fully describes parameters and annotations provide key traits, the description covers output structure (foreign principal, PDF URL), limitations (capped), and filter behavior. It is complete for a read-only listing tool, though 'Keyless' is vague.

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 all parameters. The description reinforces the source of registration_number and mentions client-side filtering, but does not add significant new meaning beyond the schema.

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 it lists FARA filings for a registrant by registration_number, specifies document types (registration statements, supplemental, etc.), and references the sibling tool search_registrants, distinguishing its purpose.

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 indicates that registration_number comes from search_registrants, and mentions optional client-side filters by document_type or country. It lacks explicit when-not-to-use guidance, but provides clear context for use.

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

All Fara toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources