Skip to main content
Glama

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

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

Beyond the readOnly/idempotent annotations, the description discloses substantial behavior: parallel fan-out across sources, return shape highlights, fallback chains, soft-fail behavior for patents, and explicit 'resolved:false' handling for private companies. It also explains that sources_failed indicates real absences, not bugs, which is highly useful operational context.

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 every clause adds functional detail: trigger phrases, input forms, source fan-out, return keys, fallback behavior, and failure semantics. It is front-loaded with the core purpose and usage guidance. Slightly dense and run-on, but not padded.

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?

There is no output schema, so the description carries the full burden of explaining return values — and it does, enumerating cik, resolved_to/from, recent_filings URIs, fundamentals, and each source section. It covers inputs, outputs, failure modes, and acceptance criteria, leaving little ambiguity for a complex multi-source tool.

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 already 100%, and the description goes further by giving concrete example values, explaining that type accepts 'company' or 'ticker' interchangeably, and detailing how values resolve via SEC EDGAR company-name matching. This meaningfully enriches the schema's bare parameter descriptions.

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?

Clearly states this is a 'full cross-source profile of a US public company in ONE parallel call' and grounds the purpose with concrete user phrasings like 'Tell me about X' and 'brief me on Tesla'. It distinguishes itself from single-pack SEC/XBRL/news lookups and names the output domains, making the tool's role unmistakable among siblings.

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 guidance: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also clarifies edge-case behavior for private companies and explains that empty sections are expected rather than failures, which prevents misinvocation.

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

All Udbud 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.8/5.0
Disambiguation2/5

Several tools form near-overlapping clusters: ask_pipeworx and ask_pipeworx_beta are explicitly identical in behavior, while ask_pipeworx, ask_pipeworx_grounded, and deep_research have overlapping scopes. The five polymarket tools also share a common prediction-market domain and could be confused despite detailed descriptions. Some boundaries between 'meta' tools such as discover_tools, suggest_questions, and ask_pipeworx are also fuzzy.

Naming Consistency3/5

The majority of tools use lowercase snake_case and many follow a verb_noun pattern (ask_pipexors, search_within, generate_llms_txt, destroy_tools), which is readable. However, there are inconsistent orderings like ai_visibility_check and dk_tender_search, plus several one-word verb tools (remember, forget, recall) alongside noun_verb forms. So the style is mostly regular but does not follow a single consistent pattern.

Tool Count2/5

34 tools is very ot heavy for a general-purpose data platform, but the server name 'Udbud Dk' implies a narrow Danish tender scope. Only 3 of the 34 tools actually concern Danish procurement, while the rest form a broad question-answering, prediction-market, subscription, and memory platform. The count feels bloated and mismatched relative to the apparent server focus.

Completeness3/5

For the broad data domain, the server covers a wide range: lookup, grounded answers, entity resolution, fact-checking, company profiles, comparisons, change feeds, polymarket opportunities, subscriptions, and memory. But relative to the Danish tender scope implied by the server name, only search/detail/recent exist and missing functionality such as saved searches or notifications for new notices. There are also some odd gaps such as no-direct citation-lookup tool, but the generous question-answering tools compensate.

Resources