Skip to main content
Glama

Spain Tenders

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

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

Annotations already mark this read-only/idempotent, and the description adds substantial behavioral detail: multi-source fan-out, USPTO soft-fail behavior, empty sections meaning genuine 'no data', private companies returning resolved:false, and type/value interchangeability. No contradiction exists between the description and 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 long, but it is front-loaded with illustrative invocations and a plain statement of the tool's role, and every listed source or failure mode earns its place. There is minor redundancy around accepted value shapes appearing both early and later, but the density is justified by the tool's breadth.

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?

Despite having no output schema, the description specifies the return sections, per-source failure semantics, input resolution behavior, and edge cases like private companies and absent FDA products. This is sufficient for an agent to invoke the tool correctly and interpret results, even without a structured output definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents both parameters at 100% coverage, but the description adds meaning beyond it: type accepts 'company' or 'ticker' interchangeably, value can be a ticker, zero-padded CIK, or company name, and names resolve via SEC EDGAR company-name match. This enriches the agent's understanding of accepted input semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's specific capability: building a 'full cross-source profile of a US public company in ONE parallel call' and enumerates the fan-out sources. This distinguishes it from single-topic lookups like resolve_entity or single-pack SEC/news tools. It does not explicitly differentiate from similarly broad siblings like deep_research or compare_entities.

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 explicitly instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' defining when it should be selected. It also gives clear accepted input shapes and private-company behavior. It stops short of naming alternatives for other use cases, such as comparisons or open-ended multi-topic research.

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

All Spain Tenders 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.7/5.0
Disambiguation2/5

Several clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (the beta currently matches stable exactly), and the Polymarket tools all circle around edge/arbitrage detection with fuzzy boundaries. The Spain tender tools and utility tools are distinct, but the overlapping clusters are enough to cause misselection.

Naming Consistency3/5

Names are uniformly snake_case and some families share clear prefixes (es_tender_*, ask_pipeworx_*, polymarket_*). However, conventions are mixed: verb-led names like compare_entities and subscribe sit alongside noun phrases like entity_profile and bet_research, so there is no consistent verb_noun pattern.

Tool Count2/5

34 tools is already in the heavy range, but the bigger problem is scope: a server named 'Spain Tenders' ships 34 tools, only 3 of which are actually Spanish-procurement tools. The rest are a broad Pipeworx/Polymarket/utility toolkit, making the count inappropriate for the declared purpose.

Completeness3/5

The three es_tender_* tools cover the core discovery workflows: keyword search, recent notices, and status filtering with budgets, deadlines, and URLs. Notable gaps remain, though: no tender detail-by-id tool, no tender-specific subscription/alerting, and no explicit region, CPV, or date-range filters.

Resources