Skip to main content
Glama
Sign In

YRUZ x402 tools

by io.github.xzntexe
OverviewDiscussionsAdmin

YRUZ TenderGraph Authority Profile (0.01 USDC)

tenders_get_authority
Read-onlyIdempotent

Procurement profile of a contracting authority from its TED notices: notice counts by type (calls, awards, amendments, prior information), the most recent notices, CPV divisions and procedure types in the recent sample, name variants and identifiers seen, first and last publication in the sample. Sample size and coverage are stated with every aggregate. Price: 0.01 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_authority"}. Same tool over HTTP: https://yruz.one/api/tenders/authority?name=Ministry+of+Finance&country=RS

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": {
      "name": "<name>"
    },
    "name": "tenders_get_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage, 2 letters (default en)
nameYesauthority name or part of it (required), e.g. Ministry of Finance
countryNobuyer country, ISO code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country / examples
      Added value: +[
+  "RS"
+]
    • addedInput schema / properties / name / examples
      Added value: +[
+  "Ministry of Finance"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses complex, non-standard behavioral traits not covered by annotations, specifically the pricing model (0.01 USDC per call), payment mechanism (x402), and error handling (returns 'PaymentRequired' if unpaid).

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 necessary for the tool's complexity, and it is structured logically: what it is, what it contains, how it's paid for, and how to call it.

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?

Since no output schema is provided, the description provides a highly detailed breakdown of the data points returned (notice counts, CPV divisions, name variants, coverage statements). This makes it exceptionally complete for a read-only profile tool.

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?

Since schema coverage is 100%, the description does not need to explain parameters, but it provides high-value context on the tool's functionality (e.g., 'authority name or part of it'), earning a score above the baseline 3.

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 clearly states the purpose is to provide the 'Procurement profile of a contracting authority' and details exactly what components make up this profile, distinguishing it from other tender retrieval tools.

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 provides specific guidance on how to invoke the tool (example JSON vs. HTTP URL) and details the payment structure, which is critical operational usage guidance.

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