Skip to main content
Glama
Sign In
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

eu_ted_tenders_scraper

Extracts European Union TED public procurement notices so users can identify tender opportunities and procurement leads.

Instructions

EU TED Public Procurement Tenders API: Extracts European Union Tenders Electronic Daily (TED) public procurement notices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eu_ted_tenders_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says only that the tool extracts notices and does not disclose authentication needs, rate limits, pagination, data freshness, read-only behavior, or return shape.

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 a single front-loaded sentence with no filler. It is efficient, though it could be slightly more structured for a scraper definition.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter scraper, the description identifies the source and action adequately. However, with no output schema and no annotations, it leaves gaps about what structured items contain and operational limits.

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 description coverage is 100%, and maxResults is already documented in the schema. The description adds no additional meaning about the parameter, so the baseline of 3 is appropriate.

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?

States a specific verb, "Extracts," and a specific resource, "European Union Tenders Electronic Daily (TED) public procurement notices." The EU/TED scope distinguishes it from procurement siblings such as us_uk_gov_contracts_procurement_scraper, though it does not explicitly name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no explicit when-to-use guidance, no exclusions, and no mention of alternatives. Usage is only implied by the EU TED scope.

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

Deploy Server

Other Tools