Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_starknet

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and that data is live from DefiLlama. Left unspecified are rate limits, latency, and whether the pay-per-call model implies retry or idempotency behavior.

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?

Roughly four short clauses: what you get, what it costs, the auth model, and the endpoint. The 'Paid.' lead and the price/payment sentence are front-loaded where an agent will see them before committing. The raw URL is arguably redundant with a machine-consumed tool definition but is cheap and does not obscure the essentials.

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 supplies enough to call correctly and to know what comes back conceptually (TVL value plus 1d/7d/30d changes). The one gap is that without an output schema, the exact field names and units of the returned payload are not spelled out.

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 the baseline is 4 and there is nothing further for the description to disambiguate. The description correctly implies no inputs are needed by framing the chain as fixed in the tool identity.

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 exact resource and scope: Starknet DeFi total value locked, live, with 1d/7d/30d change, sourced from DefiLlama. The chain name in the text is what separates it from the ~60 sibling buy_tvl_* tools, so the agent can distinguish it without opening the schema. It falls short of 5 only because the action itself ('buy'/purchase a paid API call) is conveyed obliquely through the price sentence rather than a direct verb.

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 rather than stated: the agent infers 'call this when you need Starknet TVL' from the content line. There is no explicit when-to-use or when-not-to-use guidance, and no routing to related siblings such as buy_yields_chain_starknet or buy_crypto_price that an agent might weigh against it.

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