Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Token Approvals

octav_get_approvals
Read-only

Retrieve ERC-20 token approvals (allowances) a wallet has granted to spender contracts on a specific chain, with pagination for iterating through results.

Instructions

Get the ERC-20 token approvals (allowances) a wallet has granted to spender contracts on one chain. Paginated: pass the returned cursor to get the next page; there are no more pages when it is absent or null. Costs 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>",
      "chain": "<chain>"
    },
    "name": "octav_get_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain key: arbitrum, avalanche, base, binance, ethereum, gnosis, linea, optimism or polygon
limitNoApprovals per page (default: 25, max: 100)
cursorNoCursor from a previous response, to fetch the next page
addressYesEVM wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / chain / description
      Previous value: -"Chain key: arbitrum, avalanche, base, binance, ethereum, fantom, gnosis, linea, optimism or polygon"New value: +"Chain key: arbitrum, avalanche, base, binance, ethereum, gnosis, linea, optimism or polygon"
  2. Addedv1.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral facts: pagination via cursor, the termination condition (absent or null cursor), and a cost of 1 credit. It does not describe the shape of returned approval records, but goes meaningfully beyond the annotations.

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?

Three short sentences with zero filler: the resource and scope come first, then pagination mechanics, then cost. Every sentence carries distinct information.

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 read-only paginated listing with a fully documented schema and no output schema, the definition covers scope, paging, and cost. What remains thin is the return payload (e.g., whether spender labels, amounts, or risk indicators are included), which is mild because the schema carries the inputs.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the cursor: it must come from a prior response and its absence/null signals the last page. That termination rule is not in the schema, which merely says 'cursor from a previous response.'

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 verb and resource: fetching ERC-20 approvals/allowances granted by a wallet to spender contracts, explicitly scoped to a single chain. This is precise enough to distinguish it from sibling tools like octav_get_token_overview or octav_get_wallet.

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 description (a wallet's outstanding allowances on one chain), but there is no explicit when-to-use guidance, no prerequisites, and no named alternative for related questions. No exclusions or boundaries are stated.

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