Skip to main content
Glama

list_extensions

Read-onlyIdempotent

[READ] List active extension-credit obligations (extender -> recipient vouches backed by a bonded SOL stake). Optionally filter by extender or recipient wallet (base58). Returns { extensions: [{ extender, recipient, bond_lamports }], count }. Live on Solana mainnet.

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": "list_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
extenderNoFilter to extensions where this wallet is the extender (base58).
recipientNoFilter to extensions where this wallet is the recipient (base58).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only/idempotent behavior; the description adds the return shape, filter semantics, and the 'Live on Solana mainnet' context, going beyond what annotations alone provide. No contradiction exists.

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?

Four dense, short sentences front-load the core action, then add filters, return shape, and network context. There is no fluff, repetition, or wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with fully documented optional parameters and strong annotations, the description covers return format, filtering, and runtime environment. Nothing needed to call it correctly is missing.

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 description coverage is 100%, with each parameter already explaining its purpose and format. The description only restates the filters and 'base58' without adding deeper semantics, so the baseline score of 3 applies.

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?

The description names a specific verb and resource ('List active extension-credit obligations') and clarifies the domain with the parenthetical extender/recipient vouch model. This is unambiguous and distinct from any sibling tool by name or function.

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

Usage Guidelines4/5

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

The description states optional filters by `extender` or `recipient`, telling the agent when to narrow results. It doesn't explicitly contrast with alternatives, but no sibling appears to perform the same function, so usage context is clear enough.

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