Skip to main content
Glama

Overpass

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?

Beyond annotations (readOnly, idempotent, openWorld), the description discloses detailed behavior: it fans out across multiple sources (SEC, XBRL, USPTO, GDELT, GLEIF), returns specific fields, includes a soft-fail note for the USPTO PatentsView sunset, and explains fallback logic (GDELT→GNews). This adds meaningful context about what the tool does and its limitations.

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 dense and front-loaded with example queries, then defines scope, return data, and parameter constraints. While longer than average, every sentence carries useful information and the structure is logical. Slightly verbose but well-organized.

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 there is no output schema, the description thoroughly explains return values (cik, filings, fundamentals, patents, news, LEI) and provides sufficient context for a multi-source tool. It also covers edge cases (name inputs, patent API sunset) and aligns with sibling usage, making it highly complete.

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 description coverage is 100% with detailed descriptions for both 'type' and 'value', including enumeration and formatting examples. The description reinforces the schema but does not add significant new parameter-level semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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 identifies the tool as building a full cross-source profile for a US public company, with specific verbs like 'profile', 'brief me', and 'rundown'. It distinguishes itself from siblings by explicitly noting it should be preferred over chaining single-pack lookups and by referencing resolve_entity for name inputs.

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 when-to-use examples ('Tell me about X', 'research Acme') and a direct preference statement for holistic views. It also gives a clear alternative: use resolve_entity first if only a name is available, and notes that names are not supported.

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

All Overpass 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.8/5.0
Disambiguation3/5

Most tools have distinct purposes, but the ask_pipeworx trio (stable, beta, grounded) are near-identical variants, and the five polymarket_* tools plus bet_research heavily overlap in the edge-finding space. Detailed descriptions help, but an agent could easily misselect among these clusters.

Naming Consistency3/5

Names are all snake_case and readable, but conventions vary: ask_pipeworx_* uses a prefix pattern, polymarket_* is consistent, yet others mix verbs (scan_competitor_ai_presence, generate_llms_txt) with nouns (entity_profile, resolve_entity). No single verb_noun pattern governs the set.

Tool Count2/5

34 tools is well above the 25-tool threshold and feels like multiple servers merged into one: structured data routing, prediction markets, OSM, memory, subscriptions, and AI-visibility checks. The breadth is impressive but the count is heavy for a single tool surface.

Completeness4/5

The surface is notably complete for its blended domain: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe, data access has multiple router modes plus deep research and claim validation, and prediction markets have research, edge, arbitrage, fill-risk, and cross-venue tools. Minor gaps exist (no subscription update, no explicit reverse-geocoding tool), but core workflows are covered.

Resources