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 a yieldhunter opportunity id (poolId / opportunityId / id) or protocolSlug. 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

TableJSON Schema

Name	Required	Description
`id`	No	Same as yieldhunter opportunities[].id.
`asset`	No	Stablecoin symbol, e.g. "USDC".
`chain`	No	ethereum \| base \| arbitrum
`poolId`	No	yieldhunter 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	Protocol slug, e.g. "aave-v3".
`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.

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

A3.8/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is clear. The description adds behavioral context: incomplete data yields 'review/unknown', presets affect exclusion behavior, requireCurated uses an allowlist, and it explicitly states this is research only, never holds keys, and is not an exit signal. This goes beyond annotations, though it could mention rate limits or latency.

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

Conciseness3/5

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

The description is front-loaded with the core purpose and key usage rule, but it is somewhat repetitive: policyPreset options are listed twice, and the requireCurated behavior is restated. The example is useful but adds length. Every sentence mostly earns its place, but there is redundancy.

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?

Given 18 parameters, no output schema, and rich annotations, the description covers the essential behavioral traits: what happens with no policy, how presets work, what requireCurated means, and that scoring is not approval. It also clarifies the return (PolicyVerdict + A2H). It could be more complete by describing pagination or the exact fields of PolicyVerdict, but for a research tool with no output schema, it is sufficient.

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%, meaning every parameter is documented in the schema. The description repeats some parameter examples (poolId, policyPreset, minScore, etc.) but adds no new semantic meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Evaluate a described stablecoin yield position against a research policy (pull).' This is clear and distinguishes the tool from the sibling 'health' tool, which serves a different purpose. However, it does not explicitly differentiate itself from alternatives beyond the single sibling, and the parenthetical '(pull)' is cryptic.

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?

Provides explicit when-to-use condition: 'Always pass your policy rules (or a preset). Without a policy, no meaningful check is possible — the verdict will be review/unknown, never ok.' It also specifies what is required for a real check. However, it does not explicitly state when NOT to use this tool or name alternatives (there is only one sibling, 'health', which is unrelated).

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