Skip to main content
Glama

Energi Data Dk

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

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses parallel fan-out, GDELT-to-GNews fallback, the meaning of sources_used/sources_failed, expected empty FDA sections for small-molecule companies, and resolved:false outputs for private companies. There is 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 description is front-loaded with example requests and a one-line purpose, and nearly every sentence adds useful operational detail. But the middle return-field listing is long, semicolon-dense, and slightly telegraphic in spots such as 'patents (USPTO...)'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 compensates well by enumerating most returned sections, source fallbacks, and edge cases. A few sections such as patents and news mentions remain underspecified, so it is very complete but not fully exhaustive.

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% and the schema already documents that type values are interchangeable and that value accepts ticker, zero-padded CIK, or company name. The description mostly repeats those facts with the same examples, adding no new parameter-level 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?

The description states a specific deliverable: 'full cross-source profile of a US public company in ONE parallel call,' backed by example user intents. It distinguishes the tool from single-source or lookup-only siblings by emphasizing the holistic, cross-source nature.

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?

It explicitly instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving a clear selection rule. It also states the accepted input forms and the behavior for private companies, so an agent knows when the tool is appropriate.

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

All Energi Data Dk 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.9/5.0
Disambiguation2/5

Several tools form overlapping clusters that are hard for an agent to distinguish: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, discover_tools, and suggest_questions all cover factual/research lookups, and the five Polymarket tools also overlap heavily. ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, making misselection essentially guaranteed in that pair. The descriptions are detailed, but the boundaries between many tools remain unclear at the set level.

Naming Consistency4/5

Almost all tool names are snake_case and mostly follow readable verb_noun or domain-specific patterns, such as ask_pipeworx*, resolve_entity, validate_claim, and polymarket_*. Minor deviations exist — bare verbs like remember/recall/forget/subscribe and noun-style names like spot_prices/co2_intensity — but there is no mixed casing and the overall pattern is predictable.

Tool Count2/5

34 tools is already over the 25+ threshold for a well-scoped server, and the mismatch is much worse because only three tools (co2_intensity, spot_prices, query_dataset) relate to the advertised Energi Data DK domain. The other 31 tools appear to belong to an unrelated general-purpose Pipeworx platform, so the count is not appropriate for the server's stated purpose.

Completeness3/5

For the stated Energi Data DK domain, energy data access is partially covered: two dedicated tools plus query_dataset as a generic escape hatch for all ~100 datasets prevents hard dead ends, but there are no typed tools for most of those datasets and no energy-specific monitoring/alerting. If the real intended domain is the broader Pipeworx platform, coverage is much stronger, but then the server name is misleading.

Resources