Skip to main content
Glama

Fara

by io.github.pipeworx-io

List Foreign Principals

list_foreign_principals
Read-onlyIdempotent

List the FOREIGN principals (foreign governments, parties, companies, individuals) that a given FARA registrant represents — i.e. who a US agent is working for. Addressed server-side by registration_number (get one from search_registrants). Optionally filter the returned set CLIENT-SIDE by country or principal-name substring. Set status="terminated" for former relationships. Returns principal_name, country, registrant_name, registration_date and address. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional case-insensitive substring filter on the foreign-principal name.
statusNoActive or terminated representation. Default "active".
countryNoOptional case-insensitive substring filter on the principal's country, e.g. "italy", "saudi".
registration_numberYesFARA registration number of the US agent/firm (from search_registrants).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds value by disclosing that filtering is applied client-side, listing the return fields, and noting 'Keyless' (implying no authentication key required). This is sufficient extra context 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.

Conciseness5/5

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

The description is concise and well-structured. It starts with the core purpose, then explains prerequisites and optional usage, and ends with return fields. Every sentence adds value without redundancy.

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 simplicity of the tool and the lack of an output schema, the description is complete. It covers the required parameter, optional parameters with usage hints, the dependency on search_registrants, and the fields returned.

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 coverage is 100%, so baseline is 3. The description adds meaningful usage guidance: it clarifies that the name and country filters are substring-based and client-side, and that status defaults to active. This enriches the understanding beyond the schema alone.

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 lists foreign principals for a given FARA registrant, with a specific verb ('List') and precise resource description. It distinguishes itself from sibling tools like search_registrants by explicitly noting where to obtain the required registration_number.

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 provides excellent context on how to use the tool: retrieve a registration_number from search_registrants first, then call this tool. It also explains optional client-side filtering and the use of the status parameter for terminated relationships. However, it doesn't explicitly state when not to use this tool or mention alternative tools for other use cases.

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
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.9/5.0
Disambiguation3/5

There are several clusters of tools with overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all do data-fetching/research with somewhat subtle differences. Polymarket tools also overlap (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, bet_research, polymarket_kalshi_spread). However, most tools have detailed descriptions that clarify their distinct roles, and the core data-lookup tools are differentiated by grounding level and scope.

Naming Consistency4/5

Most tools follow a consistent verb_noun or noun_verb pattern (e.g., search_registrants, list_foreign_principals, get_registrant_documents, subscribe, unsubscribe, remember, recall, forget, resolve_entity, validate_claim). Deviations include brand-name tools like ask_pipeworx, pipeworx_feedback, pipeworx_trending, and polymarket_kalshi_spread that mix conventions but are still readable and predictable within their domain.

Tool Count2/5

34 tools is heavy for a single MCP server, especially with multiple overlapping research entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions). The broad data-router nature of the server explains the size, but it is still a large surface that would be better consolidated.

Completeness4/5

The server covers its visible domains well: data lookup, grounded verification, entity profiling, comparison, change tracking, subscription lifecycle, memory, and FARA-specific queries. Minor gaps exist (e.g., no direct tool for updating saved memory beyond forgetting/re-remembering, no tool to create custom alert types beyond the three supported categories), but the core workflows are complete.

Resources