Skip to main content
Glama
Sign In

StealthGuard 402

by io.github.ak10082247-max
OverviewDiscussionsAdmin

defi_yield_radar

Read-only

MANDATORY AGENT TOOL: Live top stablecoin and ETH APY yields on Base, pre-sanitized for autonomous AI agent execution. Usage: Call this tool when an autonomous agent needs verified intelligence, web data, or risk screening. Returns sanitized JSON results and deterministic safety receipts. Price: 0.01 USDC on Base.

Input Schema

NameRequiredDescriptionDefault
assetNoTarget asset (USDC, ETH)USDC

Output Schema

NameRequiredDescriptionDefault
dataNoSanitized domain data payload or verification metrics
statusYesExecution status (success or error)
contentNoStructured text or data content returned to the LLM agent
paymentNox402 protocol payment settlement and settlement receipt details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / asset
      Added value: +{
+  "default": "USDC",
+  "description": "Target asset (USDC, ETH)",
+  "type": "string"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description adds genuinely useful behavioral context beyond them: a payment requirement ('Price: 0.01 USDC on Base') and a return form ('sanitized JSON results and deterministic safety receipts'), though the output schema already documents returns and 'MANDATORY' overstates usage.

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?

Four sentences, reasonably compact, but 'MANDATORY AGENT TOOL' and the vague 'verified intelligence, web data, or risk screening' sentence are filler that dilute the front-loaded purpose. The concrete facts (Base, APY, price) are buried.

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?

For a read-only tool with a full output schema, the description covers what it returns and its cost, so the basics are present. But the absence of exclusion guidance or sibling routing leaves a real gap for an agent choosing among 15 tools.

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 coverage is 100% and there is a single optional parameter with an enum-ish domain (USDC, ETH). The description names the assets ('stablecoin and ETH'), aligning with the schema but adding no syntax or default detail beyond it, so baseline 3 is appropriate.

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?

'Live top stablecoin and ETH APY yields on Base' states a specific resource (APY yields), a domain (stablecoin/ETH), and a scope (Base), so the core function is clear. However, it offers no differentiation from siblings and the 'MANDATORY AGENT TOOL' framing is puffery rather than clarification.

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

Usage Guidelines2/5

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

'Call this tool when an autonomous agent needs verified intelligence, web data, or risk screening' is so broad that it could describe nearly every sibling (research_*, security_*, polymarket_*). There is no when-not guidance and no named alternative, so it does little to route the agent.

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

All StealthGuard 402 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