Skip to main content
Glama

Opencitations

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

TDQS

A4.6/5.0
Behavior5/5

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

The description is rich with behavioral context beyond the readOnlyHint annotation: it discloses the parallel fan-out across multiple sources (SEC EDGAR, XBRL, USPTO, GDELT→GNews, GLEIF), details specific return fields, and warns about the USPTO PatentsView API sunset with a 'soft-fails until reactivated' behavior. No contradiction with 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 long but densely packed with essential details: usage examples, purpose, alternatives, output components, and fallback behaviors. It front-loads example queries and purpose before diving into output specifics. A slight deduction for length and some repetition of 'names not supported' and 'ALWAYS PREFER' phrasing.

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?

Despite lacking an output schema, the description enumerates all returned fields (cik + company_name, recent_filings with URIs, fundamentals, patents, news, LEI) and notes limitations (patents soft-fail, names not supported). This gives an agent complete guidance for selection and invocation expectations.

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 100% (both 'type' and 'value' have detailed descriptions). The tool description mostly restates the same parameter information (accepted ticker/CIK, names not supported), adding no new semantic value beyond the schema. It does provide example values ('AAPL', '0000320193') but these are also present in 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 the tool's function: 'full cross-source profile of a US public company in ONE parallel call.' It specifies the resource (US public companies) and the verb ('profile'), and distinguishes it from alternatives by explicitly advising 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.'

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?

Provides explicit usage triggers with example user queries ('Tell me about X', 'research Acme', etc.) and when-not conditions: 'names not supported (use resolve_entity first if you only have a name).' It also names the alternative (resolve_entity) and the broader strategy (prefer over chaining).

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

All Opencitations 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.7/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical router variants, and entity_profile/compare_entities/recent_changes/ai_visibility_check all inspect companies from overlapping angles. The six Polymarket tools form a tightly-overlapping mini-domain that further crowds the surface.

Naming Consistency3/5

All names are snake_case, but verbs are inconsistently used: many tools are noun phrases (citation_count, entity_profile, polymarket_edges) while others start with verbs (ask_pipeworx, compare_entities, validate_claim). Some prefixes like ask_* and polymarket_* help, but the overall verb/noun pattern is not coherent.

Tool Count2/5

37 tools is well above the typical 3–15 tool scope, and several are redundant variants (three ask_pipeworx modes) or hyper-specific sub-tools (six Polymarket tools). The server name suggests a focused citation service, but only six tools actually address citations, leaving the set bloated with unrelated data query and memory utilities.

Completeness3/5

For a general data-query gateway, the surface is quite broad and covers lookup, profiling, comparisons, subscriptions, and memory. But as an OpenCitations server it lacks a way to discover papers by topic and the breadth of the other domains is unwieldy and unowned—so notable gaps exist in any plausible stated purpose.

Resources