Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ TenderGraph Notice (0.004 USDC)

tenders_get_notice
Read-onlyIdempotent

One TED notice by its publication number, normalized: notice and form type, lifecycle stage, title and description, buyer with identifiers, CPV codes, procedure type, place of performance, estimated values (procedure and lots, with currency), lot titles and submission deadlines, duration, submission URL, and for results the winners, winner size and country, tender and award values and contract dates as published. With official HTML, PDF and XML links and the changes YRUZ observed since an earlier look. Price: 0.004 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_get_notice"}. Same tool over HTTP: https://yruz.one/api/tenders/notice?id=645054-2026

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesTED publication number (required), e.g. 645054-2026
langNolanguage, 2 letters (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / examples
      Added value: +[
+  "645054-2026"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses the paid x402 model, cost, supported payment chains, invalid-input handling, no-charge-on-failure behavior, and the PaymentRequired response without payment. These are meaningful behavioral details an agent needs before invoking a paid tool.

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 purpose is front-loaded and the long field inventory is useful because there is no output schema. The description is somewhat run-on and could be tightened, but it does not waste much space on irrelevant material.

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 paid, read-only lookup with no output schema, the description is complete enough: it enumerates returned fields, notes link formats and observed changes, and explains payment, failure, and unpaid-call behavior. It also provides an invocation example and an HTTP equivalent.

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 both parameters are already documented in the input schema. The description reinforces the required id as a publication number but does not add syntax or meaning for lang beyond what the schema provides.

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 resource and scope: one TED notice identified by its publication number, normalized. This clearly distinguishes it from broader siblings like tenders_search and from award/deadline-specific siblings.

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 for use: when the caller has a TED publication number and wants that single notice. It does not explicitly route callers to alternatives such as tenders_search for lookup or tenders_get_awards for award-only queries.

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 toolsInspect
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.

Resources