Skip to main content
Glama

Federal Register

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior, and the description adds substantial context beyond that: USPTO PatentsView API sunset and soft-fail behavior, FDA section being empty for companies without biologics, source success/failure reporting, and name-resolution behavior via SEC EDGAR. These details help the agent interpret results correctly rather than misreading empty data as errors.

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 front-loaded with illustrative user queries and a clear value proposition before diving into field-by-field behavior. It is dense and uses one long run-on structure, but nearly every clause contributes necessary information about failure modes and return expectations, so the length is mostly justified.

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?

With no output schema, the description carries the full burden of explaining what the tool returns, and it does so comprehensively: CIK, company name, filings with pipeworx URIs, fundamentals, patents, contracts, FDA products, hiring data, news, LEI, plus sources_used and sources_failed. It also covers input resolution failure and expected empty sections, making it complete for safe invocation and result interpretation.

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 the baseline is 3, but the description meaningfully augments both parameters: it states that type accepts 'company' or 'ticker' interchangeably, that value can be a ticker, zero-padded CIK, or company name, and that names resolve via SEC EDGAR's company-name match. It adds behavioral semantics beyond the schema's field descriptions without contradicting them.

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 opens with concrete query phrasings ('Tell me about X', 'brief me on Tesla') and defines the resource: a full cross-source profile of a US public company. It distinguishes itself from sibling lookups by emphasizing that it fans out across SEC, XBRL, patents, contracts, FDA, hiring, news, and GLEIF in one parallel call.

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?

It explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving clear selection criteria relative to more granular alternatives. It also covers expected edge cases like private companies returning resolved:false instead of failing, and empty sections being real 'no data' rather than bugs.

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

All Federal Register 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.5/5.0
Disambiguation1/5

Several tools are nearly indistinguishable: ask_pipeworx and ask_pipeworx_beta are explicitly identical in behavior, and ask_pipeworx_grounded overlaps heavily with them. Additionally, entity_profile, compare_entities, deep_research, and validate_claim all cover similar company/factual research territory, creating frequent selection ambiguity.

Naming Consistency2/5

Naming mixes multiple conventions: descriptive lowercase phrases (ai_visibility_check, compare_entities, valid claim) coexist with verb_noun (search_documents, recent_rules) and inconsistent underscores (ask_pipeworx vs ask_pipeworx_grounded, resolve_entity). There is no single recognizable pattern.

Tool Count1/5

The server is named 'Federal Register' but only 3 of 34 tools (search_documents, recent_rules, get_document) relate to that domain. The other 31 tools form a sprawling Pipeworx data and prediction-market suite, making the count extreme and inappropriate for the declared purpose.

Completeness2/5

For the stated Federal Register domain, the surface is minimal: search, recent listing, and single-document retrieval, with no docket browsing, full-text search within documents, or agency-specific navigation. The broader Pipeworx capability set is comprehensive but irrelevant to the server's name, leaving obvious gaps for the actual purpose.

Resources