Skip to main content
Glama

Gdelt

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

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

Annotations already mark the tool read-only/idempotent, and the description adds substantial behavioral detail: it fans out across many sources, soft-fails on patents, reports sources_used/sources_failed, treats empty sections as real 'no data', and returns resolved:false with notes for private companies. 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?

The definition is long, but the tool is genuinely complex and the detail about sources, return sections, and failure modes earns its place. It is front-loaded with user phrasings and the decisive usage preference; minor redundancy with the schema and a dense wall-of-text style keep it from a 5.

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 present, the description fully enumerates the returned sections (cik, filings, fundamentals, patents, contracts, FDA products, hiring, news, LEI) plus sources_used/sources_failed. It covers failure behavior, name resolution, and the private-company case, leaving an agent with everything needed to invoke the tool correctly.

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?

The schema already documents both parameters completely, including the type enum and the accepted ticker/CIK/name forms, so the description is not strictly required to compensate. It reinforces examples and 'interchangeably' behavior but mostly repeats schema content rather than adding new meaning.

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?

States a specific verb and resource: full cross-source profile of a US public company, with concrete trigger examples ('Tell me about X', 'brief me on Tesla'). It also marks itself as the holistic alternative to single-pack lookups, separating it from siblings such as resolve_entity and search_articles.

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?

Gives explicit when-to-use triggers and says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also describes the private-company and no-data cases so the agent knows what to expect and when not to retry.

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

All Gdelt 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
Disambiguation2/5

Multiple tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), and ask_pipeworx_grounded are near-duplicates, while deep_research, entity_profile, compare_entities, and bet_research all route into the same underlying Pipeworx catalog. ai_visibility_check and scan_competitor_ai_presence also overlap heavily. Descriptions are detailed, but an agent could easily misselect among the research and market-analysis clusters.

Naming Consistency3/5

All names use lowercase snake_case, but the pattern is mixed: verb-first names (search_articles, resolve_entity, validate_claim), noun-phrase domain tools (entity_profile, polymarket_fill_risk), brand-prefixed names (pipeworx_trending, ask_pipeworx), and bare verbs (recall, remember, forget). It is readable and consistent in style, but there is no predictable verb_noun convention and tool names do not reliably indicate their domain.

Tool Count2/5

With 35 tools, this set is well beyond the 3-15 well-scoped range and even the 16-25 heavy range. Several clusters could be consolidated (three ask_pipeworx variants, five polymarket analysis tools, three memory tools), and unrelated utilities like generate_llms_txt and scan_dependency add to the sprawl.

Completeness4/5

For a data-research server, coverage is broad: universal lookup, grounded answers, deep research, entity profiles, comparisons, news search/sentiment/timelines, prediction-market analysis, and memory/subscription lifecycle tools are all present. The main gaps are direct raw-document fetching (e.g., full article text or a specific SEC filing body), but the universal ask_pipeworx router and pipeworx:// resource URIs let agents work around those.

Resources