YRUZ x402 tools

YRUZ TenderGraph Search (0.005 USDC)

tenders_search

Read-onlyIdempotent

Search public tenders and procurement notices published in TED (EU Official Journal S, all EU/EEA countries plus EU-funded procurement such as Serbia): keywords, buyer country, CPV code, contracting authority, awarded supplier, notice type, publication and deadline date ranges and estimated value. Each notice normalized: title, buyer, CPV, procedure, estimated value with currency, lot deadlines, lifecycle stage, winners as published, and the official TED links. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"tenders_search"}. Same tool over HTTP: https://yruz.one/api/tenders/search?q=software&country=RS&limit=10

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": "tenders_search"
  }
}

Input Schema

Name	Required	Description
`q`	No	keywords in the notice text, e.g. cloud software
`cpv`	No	CPV code or prefix, 2-8 digits, e.g. 72 or 72000000
`lang`	No	language of titles, 2 letters (default en)
`page`	No	page, 1-100 (default 1)
`type`	No	competition (calls), result (awards), change (amendments), planning (prior information) or all (default)
`buyer`	No	contracting authority name contains
`limit`	No	notices per page, 1-50 (default 20)
`country`	No	buyer country, ISO code (DE, DEU, RS, SRB ...)
`supplier`	No	awarded supplier name contains (award notices)
`value_max`	No	estimated procedure value at most
`value_min`	No	estimated procedure value at least (in its own currency)
`deadline_to`	No	date YYYY-MM-DD
`published_to`	No	date YYYY-MM-DD
`deadline_from`	No	date YYYY-MM-DD
`published_from`	No	date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / country / examples
```
Added value: +[
+  "RS"
+]
```
- addedInput schema / properties / limit / examples
```
Added value: +[
+  "10"
+]
```
- addedInput schema / properties / q / examples
```
Added value: +[
+  "software"
+]
```
AddedOct 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds substantial behavioral context beyond annotations: price of 0.005 USDC per call, x402 payment flow, invalid input refused before payment, failed runs never charged, and PaymentRequired returned without payment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then covers normalized output, payment behavior, and invocation help. Despite its length, every sentence carries useful information for a paid, multi-parameter search tool, and there is no filler.

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?

For a complex 15-parameter paid search tool with no output schema, the description is complete enough: it explains what is searched, what each notice includes on return, the payment and failure behavior, and how to get invocation examples. Missing return-format details are not significant for a search endpoint.

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%, so all 15 parameters are already documented in the input schema. The description enumerates the main filter categories (keywords, country, CPV, authority, supplier, notice type, date ranges, value) but does not add syntax, defaults, or format details beyond what the schema provides.

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 states a specific verb and resource: search public tenders and procurement notices published in TED, with geographic scope (EU/EEA plus EU-funded Serbia). It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as tenders_get_notice, tenders_get_awards, or tenders_get_deadlines.

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?

It gives clear context on how the tool is used, including payment via x402, no account or API key, and a pointer to get_example for calling details. It does not state when to use this search tool instead of the more specific sibling tools like tenders_get_notice or tenders_get_awards.

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

All YRUZ x402 tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.