Skip to main content
Glama

Deepl

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

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses multiple non-obvious behaviors: the USPTO PatentsView API sunset with soft-fail, GDELT→GNews fallback, 'expected, not a failure' semantics for fda_products when a company only has small-molecule drugs, and empty sections meaning 'real no data, not a bug.' The sources_used/sources_failed mechanism gives the agent a way to diagnose partial results.

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 the tool spans 13 data sources with no output schema, so the density is earned rather than padded. Key directives ('ALWAYS PREFER') and the field enumeration are front-loaded, though the closing note about `type` accepting 'company' or 'ticker' is partially redundant with the 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 values and does so exhaustively, annotating every top-level field (cik, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, sources_used/sources_failed) with a clarifying parenthetical. Edge cases — private companies, expected empty sections, API sunset, fallback chains — are all explicitly addressed.

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%, so the baseline is 3 and the schema already documents both parameters fully. The description adds the interchangeability clarification ('both are accepted and behave identically') and restates the value shapes, but it does not go materially beyond what the schema already says.

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 leads with concrete query examples ('Tell me about X', 'research Acme', 'brief me on Tesla') and immediately defines the resource ('US public company') plus the verb ('profile') in the first sentence. It clearly distinguishes itself from single-source lookups by promising a 'full cross-source profile 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit selection rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also documents the accepted input shapes (ticker, CIK, name) and the private-company fallback (resolved:false with a notes line). However, it does not name specific sibling tools such as resolve_entity or compare_entities, nor does it state the negative case for single-purpose queries.

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

All Deepl 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

B3.3/5.0
Disambiguation2/5

Many tools have overlapping functionality, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, which are essentially the same with minor differences. The polymarket_* family also has five tools with similar names and purposes, making it easy to select the wrong one despite detailed descriptions.

Naming Consistency2/5

Tool names mix verb-first patterns (ask, generate, list, remember) with noun-first patterns (entity_profile, polymarket_arbitrage), and include camelCase like ai_visibility_check. This inconsistent naming style makes the set feel arbitrary and harder to navigate.

Tool Count3/5

With 36 tools, the server exceeds the typical well-scoped range of 3-15. While the multi-purpose nature justifies a larger set, the presence of many near-duplicates (beta/grounded variants, multiple polymarket tools) inflates the count without proportional functional gain.

Completeness4/5

The toolset covers a wide array of domains including translation, entity resolution, financial data, prediction markets, memory, subscriptions, and AI visibility. It appears very comprehensive for its intended multi-purpose server, with no obvious major gaps in core capabilities.

Resources