Skip to main content
Glama

ipinfo

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. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description adds substantial behavioral context beyond that: it fans out across named external sources, soft-fails on sunset APIs, returns empty sections as real 'no data', and reports sources_used/sources_failed. It even explains that a company with only small-molecule drugs will show no fda_products, which is expected. This is exemplary transparency.

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 nearly every sentence carries operational value, and the most important usage directive ('ALWAYS PREFER...') is front-loaded. It could be tightened in places, such as the long list of example phrasings, but the density is justified given the tool's breadth and the absence of an output schema.

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 return content, and it does so thoroughly: it enumerates every returned section, the source behind each, failure behavior, input-resolution behavior, and what resolved:false means. An agent has everything needed to call this tool correctly and interpret its result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description still adds meaning by clarifying that type values are interchangeable and value can be a ticker, zero-padded CIK, or company name, with names resolved via SEC EDGAR. It documents resolved_from/resolved_to behavior and explicitly states what happens for private companies, going well 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 states a specific verb and resource: producing a full cross-source profile of a US public company in one parallel call. It is packed with concrete example queries and enumerates the exact output sections, making it unmistakable what the tool does and how it differs from narrower single-source 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?

The description explicitly says to always prefer this tool over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. It also covers edge-case routing, such as how private companies are handled and that type accepts 'company' or 'ticker' interchangeably, leaving little ambiguity about when to invoke it.

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

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

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions; polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all scan prediction markets. Despite long descriptions, an agent could easily select the wrong one, especially the currently identical ask_pipeworx and ask_pipeworx_beta.

Naming Consistency3/5

Mostly snake_case, but with inconsistent patterns: get_my_ip/lookup_ip use verb_noun, entity_profile/recent_changes are noun phrases, remember/recall/forget are bare verbs, and the polymarket_* tools share a brand-prefixed noun style. Readable but not a predictable, uniform convention.

Tool Count2/5

At 33 tools, the server is overloaded, far exceeding the 25-tool threshold for 'too many.' It combines two unrelated identities—the original ipinfo IP lookup and the massive Pipeworx data/research platform—making the toolset heavy and harder for an agent to navigate efficiently.

Completeness4/5

The tool surface provides strong coverage of the data query and research lifecycle: discovery (discover_tools, suggest_questions), entity resolution (resolve_entity), lookup (ask_pipeworx, entity_profile), verification (validate_claim, ask_pipeworx_grounded), and post-processing (search_within, recent_changes). Minor gaps exist—for example, no dedicated 'get SEC filing by accession' tool or single-purpose financials endpoint—but these are workaroundable via the routing tools.

Resources