Yutai

Get benefit availability

get_benefit_availability

Read-only

Read the benefits the companies behind one or more tokenized stocks offer in one country, each with what a holder must do to reach it, how it is delivered, and whether it is only an example. Give one or more instrument ids and the two-letter country.

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": {
      "instruments": "<instruments>",
      "country": "<country>"
    },
    "name": "get_benefit_availability"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes	The market whose stored policy shapes the answer: its two-letter country code, such as PT.
`instruments`	Yes	The instruments to read: one or more, at most 200 in one read, each an ISIN such as US0000000009 or a CAIP-19 instrument id such as eip155:88880/erc20:0x0000000000000000000000000000000000000000.

Output Schema

Name	Required	Description	Default
`disclaimer`	Yes	The standard Yutai disclaimer for benefits.
`instruments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedOutput schema / properties / disclaimer

Added value: +{
+  "description": "The standard Yutai disclaimer for benefits.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "instruments"
-]New value: +[
+  "instruments",
+  "disclaimer"
+]

First observedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the bar is lower; the description earns credit by disclosing what each result contains (holder requirements, delivery method, example-only flag) and that the country's stored policy shapes the answer. It omits failure behavior for unknown instruments or unsupported countries.

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?

One dense sentence that front-loads the resource and then enumerates the returned fields; every clause carries information. Slightly long and comma-chained, but not padded.

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

Completeness4/5

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

With an output schema, full parameter descriptions, and safety annotations in place, the description only needs to convey intent and result shape, which it does. The remaining gap is routing relative to find_benefits and behavior on invalid inputs.

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 the schema already documents the country pattern and ISIN/CAIP-19 formats. The description only restates that instruments are ids and country is a two-letter code, adding essentially no semantics beyond the schema.

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 and resource ('Read the benefits the companies behind one or more tokenized stocks offer in one country'), with the scope narrow enough that an agent knows exactly what comes back. It never names or contrasts with the likely-confusable sibling find_benefits, so differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is implied by the description ('give one or more instrument ids and the two-letter country'), but there is no explicit when-to-use vs. when-to-use-something-else guidance, and no mention of find_benefits despite it being the obvious alternative for benefit lookups.

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

All Yutai 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.

Resources

Need Help?