yieldsentinel

Check position (research policy)

check_position

Read-onlyIdempotent

Evaluate a described stablecoin yield position against a research policy (pull).

Always pass your policy rules (or a preset). Without a policy, no meaningful check is possible — the verdict will be review/unknown, never ok.

Pass poolId from yieldhunter list_yields opportunities[].id (also accepted as opportunityId or id). That id is one market. Required for a real check: policyPreset (treasury-conservative | balanced-research | rwa-selective) and/or minScore / maxRewardShare / excludeCategories / maxExitRisk / requireCurated. Presets: treasury-conservative | balanced-research | rwa-selective. rwa-selective does not exclude RWA but is not a free pass (YS policy allowlist + higher bar). requireCurated uses the Yieldsentinel policy allowlist (curated.json), not yieldhunter scoring priors. Scoring ≠ policy approval.

Fetches live yieldhunter research (score, APY, TVL, category, rewardShare, exitRisk) and curated flags, then returns a PolicyVerdict plus A2H (summary, suggestedNextSteps, legend).

Incomplete or missing data is review/unknown — never a silent ok. A verdict is not an exit signal or execution order. Research only — never holds keys.

Example: { "poolId": "43641cf5-a92e-416b-bce9-27113d3c0db6", "policyPreset": "treasury-conservative", "notionalUsd": 10000 }

Input Schema

Name	Required	Description
`id`	No	Same as yieldhunter list_yields opportunities[].id.
`asset`	No	Stablecoin symbol, e.g. "USDC".
`chain`	No	ethereum \| base \| arbitrum. Case-insensitive. Also accepts eth, mainnet, arb, arbitrum-one.
`poolId`	No	yieldhunter list_yields opportunities[].id (DefiLlama pool UUID). Example: "43641cf5-a92e-416b-bce9-27113d3c0db6"
`minScore`	No	Minimum compositeRiskAdjusted (0–100).
`minNetApy`	No	Minimum net APY estimate.
`minTvlUsd`	No	Minimum pool TVL in USD.
`horizonDays`	No	Holding horizon in days for net-yield context (default 30).
`maxExitRisk`	No	Cap on yieldhunter exitRisk heuristic: low \| medium \| high. Unknown or above the cap → review.
`notionalUsd`	No	Research notional in USD (size hint only). Example: 10000
`policyPreset`	No	Policy preset: "treasury-conservative" \| "balanced-research" \| "rwa-selective". treasury-conservative excludes RWA; rwa-selective allows RWA but is not a free pass (YS policy allowlist + higher bar).
`protocolSlug`	No	Yieldhunter protocol slug. Prefer poolId from list_yields opportunities[].id when the protocol has more than one market.
`riskAppetite`	No	conservative \| balanced \| aggressive (research posture only).
`opportunityId`	No	Alias for poolId / id.
`maxRewardShare`	No	Maximum incentive share of gross APY (0–1).
`requireCurated`	No	If true, the protocol/pool must be on the Yieldsentinel policy allowlist (curated.json), not yieldhunter scoring priors. Missing allowlist entry → review. Scoring ≠ policy approval.
`minProtocolScore`	No	Minimum yieldhunter protocol risk score (0–100, higher = safer).
`excludeCategories`	No	Exclude categories, e.g. ["rwa"].

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 23, 2026

changedInput schema / properties / chain / description

Previous value: -"ethereum | base | arbitrum"New value: +"ethereum | base | arbitrum. Case-insensitive. Also accepts eth, mainnet, arb, arbitrum-one."

addedInput schema / properties / chain / enum

Added value: +[
+  "ethereum",
+  "base",
+  "arbitrum"
+]

addedInput schema / properties / chain / type
```
Added value: +"string"
```

changedInput schema / properties / id / description

Previous value: -"Same as yieldhunter opportunities[].id."New value: +"Same as yieldhunter list_yields opportunities[].id."

addedInput schema / properties / maxExitRisk / enum

Added value: +[
+  "low",
+  "medium",
+  "high"
+]

addedInput schema / properties / maxExitRisk / type
```
Added value: +"string"
```

addedInput schema / properties / policyPreset / enum

Added value: +[
+  "treasury-conservative",
+  "balanced-research",
+  "rwa-selective"
+]

addedInput schema / properties / policyPreset / type
```
Added value: +"string"
```

changedInput schema / properties / poolId / description

Previous value: -"yieldhunter opportunities[].id (DefiLlama pool UUID). Example: \"43641cf5-a92e-416b-bce9-27113d3c0db6\""New value: +"yieldhunter list_yields opportunities[].id (DefiLlama pool UUID). Example: \"43641cf5-a92e-416b-bce9-27113d3c0db6\""

changedInput schema / properties / protocolSlug / description

Previous value: -"Protocol slug, e.g. \"aave-v3\"."New value: +"Yieldhunter protocol slug. Prefer poolId from list_yields opportunities[].id when the protocol has more than one market."

addedInput schema / properties / riskAppetite / enum

Added value: +[
+  "conservative",
+  "balanced",
+  "aggressive"
+]

addedInput schema / properties / riskAppetite / type
```
Added value: +"string"
```

Changed28 schema fields changedSep 13, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- removedInput schema / properties / asset / minLength
```
Removed value: -1
```
- removedInput schema / properties / asset / type
```
Removed value: -"string"
```
- removedInput schema / properties / chain / enum
```
Removed value: -[
-  "ethereum",
-  "base",
-  "arbitrum"
-]
```
- removedInput schema / properties / chain / type
```
Removed value: -"string"
```
- removedInput schema / properties / excludeCategories / items
```
Removed value: -{
-  "enum": [
-    "lending",
-    "rwa",
-    "other"
-  ],
-  "type": "string"
-}
```
- removedInput schema / properties / excludeCategories / type
```
Removed value: -"array"
```
- removedInput schema / properties / horizonDays / exclusiveMinimum
```
Removed value: -0
```
- removedInput schema / properties / horizonDays / maximum
```
Removed value: -365
```
- removedInput schema / properties / horizonDays / type
```
Removed value: -"number"
```
- removedInput schema / properties / id / type
```
Removed value: -"string"
```
- removedInput schema / properties / maxExitRisk / enum
```
Removed value: -[
-  "low",
-  "medium",
-  "high"
-]
```
- removedInput schema / properties / maxExitRisk / type
```
Removed value: -"string"
```
- removedInput schema / properties / maxRewardShare / anyOf
```
Removed value: -[
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / minNetApy / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- removedInput schema / properties / minProtocolScore / anyOf
```
Removed value: -[
-  {
-    "maximum": 100,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / minScore / anyOf
```
Removed value: -[
-  {
-    "maximum": 100,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / minTvlUsd / minimum
```
Removed value: -0
```
- removedInput schema / properties / minTvlUsd / type
```
Removed value: -"number"
```
- removedInput schema / properties / notionalUsd / exclusiveMinimum
```
Removed value: -0
```
- removedInput schema / properties / notionalUsd / type
```
Removed value: -"number"
```
- removedInput schema / properties / opportunityId / type
```
Removed value: -"string"
```
- removedInput schema / properties / policyPreset / type
```
Removed value: -"string"
```
- removedInput schema / properties / poolId / type
```
Removed value: -"string"
```
- removedInput schema / properties / protocolSlug / type
```
Removed value: -"string"
```
- removedInput schema / properties / requireCurated / type
```
Removed value: -"boolean"
```
- removedInput schema / properties / riskAppetite / enum
```
Removed value: -[
-  "conservative",
-  "balanced",
-  "aggressive"
-]
```
- removedInput schema / properties / riskAppetite / type
```
Removed value: -"string"
```
Changed5 schema fields changedSep 13, 2026
- removedInput schema / properties / id / minLength
```
Removed value: -1
```
- removedInput schema / properties / opportunityId / minLength
```
Removed value: -1
```
- removedInput schema / properties / policyPreset / enum
```
Removed value: -[
-  "treasury-conservative",
-  "balanced-research",
-  "rwa-selective"
-]
```
- removedInput schema / properties / poolId / minLength
```
Removed value: -1
```
- removedInput schema / properties / protocolSlug / minLength
```
Removed value: -1
```
First observedAug 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuine context beyond them: it fetches live yieldhunter research, returns a PolicyVerdict plus A2H (summary, suggestedNextSteps, legend), degrades to review/unknown on missing data rather than a silent ok, and explicitly states it never holds keys and is not an exit/execution signal.

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?

Front-loaded with the purpose and the critical 'no policy = no verdict' warning, and the example is useful. However the preset list is stated twice and 'Scoring ≠ policy approval' appears in both the description body and the requireCurated text, which is avoidable duplication in an already dense block.

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 an 18-parameter tool with no output schema, the description covers the input contract (required policy inputs, id alias resolution), the return payload (PolicyVerdict + A2H fields), and the failure semantics (review/unknown). Nothing an agent needs to call this safely and interpret the result appears missing.

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?

Schema coverage is 100% so the baseline is 3, but the description goes further by explaining that poolId/opportunityId/id are aliases for one market and by naming the policy inputs (policyPreset, minScore, maxRewardShare, excludeCategories, maxExitRisk, requireCurated) that are needed for a real check despite schema required=0. It adds less on the scoring/notional params, which the schema already covers.

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 first sentence gives a specific verb and resource ('Evaluate a described stablecoin yield position against a research policy') and explicitly frames it as a pull. It's instantly distinguishable from the only sibling, 'health'.

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

Usage Guidelines5/5

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

It states a hard prerequisite ('Always pass your policy rules... Without a policy... the verdict will be review/unknown, never ok') and enumerates the valid policy inputs. It also routes the agent on which identifier to use ('Pass poolId from yieldhunter list_yields opportunities[].id... Prefer poolId... when the protocol has more than one market').

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

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

Check position (research policy)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources