Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_polygon

Paid. Polygon total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/defillama/tvl/polygon.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_tvl_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the cost ($0.005 USDC), the accepted payment chains (Base or Solana), the absence of account/API-key requirements, and the no-charge-on-failure policy, plus the data provenance. It omits rate limits, latency, and response/unit format, which is why it is not a 5.

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?

Information is front-loaded ('Paid.' first, then the data, then cost, then auth and failure terms), and each clause carries distinct value with no repetition. The style is telegraphic fragments rather than prose, which is efficient here but slightly terse.

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 tool with no output schema and no annotations, the description covers cost, auth, failure handling, and data source, but says nothing about how the payment is actually executed (x402 flow, wallet, endpoint invocation) or the shape/units of the returned payload. An agent knows what it will get and what it costs, but not exactly how to complete the call or consume the result.

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?

The tool takes zero parameters, so there is no schema semantics to add meaning to; the description correctly does not invent parameter details. Baseline for a parameterless tool is 4.

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 names the specific resource (Polygon DeFi TVL), the freshness (live), the metrics returned (1d/7d/30d change) and the upstream source (DefiLlama), which cleanly distinguishes it from the many sibling chain-specific buy_tvl_* tools. It is a noun phrase rather than an explicit verb+object, but an agent can still tell exactly what it obtains.

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 resource name rather than stated: there is no 'use this when you need Polygon TVL' sentence and no pointer to alternatives such as buy_yields_chain_polygon or other chain TVL siblings. The payment and 'failed calls not charged' notes do help an agent decide whether to invoke it, which lifts it above a bare minimum.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources