Skip to main content
Glama

Public Suffix List

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.8/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, open-world, non-destructive. Description adds detailed behavioral context: data sources scanned (SEC EDGAR, XBRL, USPTO, GDELT, GLEIF), specific return fields, USPTO sunset issue with soft-fail behavior, and that it takes ticker or CIK. 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?

Description is front-loaded with user-facing examples and clearly structured. While somewhat lengthy, each sentence adds necessary detail (sources, return fields, limitations). Slightly verbose but well-organized and earned.

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 no output schema, the description covers all return components: CIK, recent filings with URIs, fundamentals (specific financial fields), patents (with sunset note), news (GDELT→GNews fallback), and LEI. Also mentions limitations (names not supported, USPTO soft-fail). Thorough for a complex tool.

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% with descriptions for both parameters. Description adds value beyond schema by explaining how to use the 'value' parameter (ticker or zero-padded CIK, names not supported) and that 'type' currently only supports 'company'. This extra context justifies a score above baseline 3.

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 uses specific verbs like 'profile' and 'brief me on' with examples (Tesla, Apple) and clearly states it returns a 'full cross-source profile' of a US public company. It distinguishes from sibling tools by explicitly recommending it over chaining single-pack lookups.

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?

Explicitly states when to use ('when the user asks for a holistic view') and when not to use ('names not supported — use resolve_entity first'). Also provides alternatives like 'resolve_entity' and mentions preference over chaining.

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

All Public Suffix List 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

C2.9/5.0
Disambiguation2/5

Multiple tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all query data in similar ways. Prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) are numerous and confusingly similar. Agents will struggle to choose the right tool.

Naming Consistency2/5

Tool names follow no consistent pattern. Some use snake_case like ai_visibility_check, others are generic single words (parse, remember, forget). There is no uniform verb_noun structure, mixing descriptive names (entity_profile) with vague ones (list_version).

Tool Count3/5

35 tools is a large set for a server named 'Public Suffix List', but the actual domain (comprehensive data platform) may justify many tools. However, the count feels heavy for the apparent scope of the server, with many niche prediction market tools.

Completeness4/5

The tool surface covers a wide range: data query, comparison, subscription, memory management, and claim verification. However, there are gaps in data modification (no update/delete for records) and some prediction market features have no direct counterparts. Overall, the set is fairly complete for its data-fetching purpose.

Resources