Skip to main content
Glama
Sign In

SYNTHORA x402 Intelligence Mesh

by com.hergertsynthora
OverviewDiscussionsAdmin

defi_yields

Read-onlyIdempotent

SYNTHORA defi-yields: stablecoin DeFi yields ranked with a risk outlier detector — APY vs class median (>=3x median = the excess yield IS the risk price). Only pools with TVL >= $10M. Source: DefiLlama, free, no key. $0.01 USDC x402 Base. [x402: 0.01 USDC per call on Base]

Input Schema

NameRequiredDescriptionDefault
redNoOptional nonempty chain name, trimmed and matched case-insensitively for exact equality against captured pool.chain. Omit for all captured eligible chains. A chain outside that captured universe returns an explicit error; this does not select another data source.
desdeNoOptional timezone-aware ISO8601 cut, not in the future. Compares current eligible pools with the latest local batch at or before that cut. Changes use the full eligible universe, independently of red/activo/protocolo display filters. Missing older batches are reported; no history coverage is guaranteed.
activoNoOptional nonempty asset symbol token. It is trimmed, uppercased and matched against tokens of the pool symbol (for example USDC); not a substring, contract-address or mint lookup. Omit for all eligible symbols. A token with no matches may produce an empty selected list.
pool_idNoOptional exact pool ID for local batch-history retrieval only; it does not filter the current top-pool list. History defaults to 30 days unless historial_dias supplies 1-90. This is not a live DefiLlama history request; missing local history is disclosed as a gap.
protocoloNoOptional nonempty protocol/project identifier, such as aave-v3. Trimmed and matched case-insensitively for exact equality with pool.proyecto; not a substring or protocol-contract lookup. Omit for all projects in the captured eligible universe.
historial_diasNoRequires pool_id; history availability is not guaranteed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / activo / description
      Added value: +"Optional nonempty asset symbol token. It is trimmed, uppercased and matched against tokens of the pool symbol (for example USDC); not a substring, contract-address or mint lookup. Omit for all eligible symbols. A token with no matches may produce an empty selected list."
    • addedInput schema / properties / desde / description
      Added value: +"Optional timezone-aware ISO8601 cut, not in the future. Compares current eligible pools with the latest local batch at or before that cut. Changes use the full eligible universe, independently of red/activo/protocolo display filters. Missing older batches are reported; no history coverage is guaranteed."
    • addedInput schema / properties / pool_id / description
      Added value: +"Optional exact pool ID for local batch-history retrieval only; it does not filter the current top-pool list. History defaults to 30 days unless historial_dias supplies 1-90. This is not a live DefiLlama history request; missing local history is disclosed as a gap."
    • addedInput schema / properties / protocolo / description
      Added value: +"Optional nonempty protocol/project identifier, such as aave-v3. Trimmed and matched case-insensitively for exact equality with pool.proyecto; not a substring or protocol-contract lookup. Omit for all projects in the captured eligible universe."
    • addedInput schema / properties / red / description
      Added value: +"Optional nonempty chain name, trimmed and matched case-insensitively for exact equality against captured pool.chain. Omit for all captured eligible chains. A chain outside that captured universe returns an explicit error; this does not select another data source."
  2. Changed8 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "input": ""
-  }
-]New value: +[
+  {}
+]
    • addedInput schema / properties / activo
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / desde
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / historial_dias
      Added value: +{
+  "description": "Requires pool_id; history availability is not guaranteed.",
+  "maximum": 90,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / input
      Removed value: -{
-  "description": "SYNTHORA defi-yields: stablecoin DeFi yields ranked with a risk outlier detector — APY vs class median (>=3x median = the excess yield IS the risk price). Only pools with TVL >= $10M. Source: DefiLlam",
-  "examples": [
-    ""
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / pool_id
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / protocolo
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / red
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "input": ""
+  }
+]
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"\"}"New value: +"SYNTHORA defi-yields: stablecoin DeFi yields ranked with a risk outlier detector — APY vs class median (>=3x median = the excess yield IS the risk price). Only pools with TVL >= $10M. Source: DefiLlam"
    • addedInput schema / properties / input / examples
      Added value: +[
+  ""
+]
  4. Added
  5. Removed
  6. Added

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, idempotent, non-destructive, openWorld), so the bar is lower, and the description clears it by disclosing the data source (DefiLlama, no key), the TVL eligibility floor, and — most usefully — that calls are metered at $0.01 USDC via x402 on Base. That payment/auth context is exactly the kind of behavior annotations cannot express. No rate limits or result-size limits are mentioned.

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?

Front-loads the resource and mechanic well, but the brand prefix 'SYNTHORA defi-yields:' is filler and the payment fact is stated twice ('$0.01 USDC x402 Base' followed by '[x402: 0.01 USDC per call on Base]'). Dense and readable, yet it wastes budget on redundancy while omitting parameter guidance.

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

Completeness3/5

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

With six optional parameters, no required fields, and no output schema, the description should carry more of the return-shape burden. It does convey the metric and the outlier rule, but says nothing about how many pools come back, ordering beyond 'ranked', or how the pool_id/desde history mode differs in output from the current-list mode, leaving real gaps.

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 six parameters (red, desde, activo, pool_id, protocolo, historial_dias) are fully documented in the schema. The description adds no parameter-level detail beyond the implicit idea of a 'class' comparison; baseline 3 is appropriate when the schema does all the work.

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?

States a specific resource (stablecoin DeFi yields) plus the differentiating mechanic (APY ranked against class median with a >=3x outlier flag). This is intrinsically separable from siblings like defi_llama_tvl_ranking (TVL) and stablecoin_supply (supply), so an agent can route without opening a schema.

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?

Gives scoping context ('Only pools with TVL >= $10M') and interpretive guidance ('>=3x median = the excess yield IS the risk price'), which shapes how results should be read. It never states when to prefer this over a sibling or when it is the wrong tool, so usage is implied rather than directed.

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

All SYNTHORA x402 Intelligence Mesh 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