Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_plasma

Paid. Plasma 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/plasma.

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_plasma"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does a fair job: it discloses that the call is paid, the exact price ($0.005 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, payment mechanism details, and any latency/refresh behavior, but the cost-and-auth profile is unusually well covered.

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

Conciseness5/5

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

Extremely dense and front-loaded: resource and payload first, then pricing, auth, failure policy, then the endpoint. Every clause adds a fact an agent would otherwise have to discover, and there is no filler.

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?

For a zero-parameter, no-output-schema tool, the description covers what it returns, its cost, its auth requirements, and its failure semantics, plus the direct URL. The only shortfall is that the payment flow itself (how the USDC is actually charged) is not described, which matters because the tool is paid.

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 no parameters, so the baseline is 4 and there is nothing for the description to explain beyond that. The description correctly implies a parameterless single-resource fetch, consistent with the empty schema.

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?

States the exact resource (Plasma total value locked in DeFi) and the payload shape (live value plus 1d/7d/30d change, DefiLlama source), so an agent knows precisely what it returns. It does not explicitly say 'for other chains use buy_tvl_<chain>', but the Plasma-specific naming and data description separate it from the ~60 sibling chain tools well enough.

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 itself (call it when you want Plasma TVL), and the price/failure terms help the agent decide whether to spend money. There is no explicit when-not-to-use guidance and no pointer to adjacent alternatives such as buy_yields_chain_plasma or the other buy_tvl_* chain variants, leaving routing to inference.

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