agent-toolbelt

List Available Tools

list_tools

Discover available API tools in the Agent Toolbelt catalog with descriptions and pricing information.

Instructions

List all tools available in the Agent Toolbelt API catalog, including descriptions and pricing.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully adds critical context about return content ('including descriptions and pricing'), informing the agent what data to expect despite the absence of an output schema. It could additionally clarify that this is a safe, read-only operation.

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?

The description is a single, efficient sentence of 13 words with zero waste. It is front-loaded with the primary action ('List all tools') and packs essential qualifying details (scope: 'Agent Toolbelt API catalog'; return values: 'descriptions and pricing') into minimal space.

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?

Given the tool's simplicity (zero parameters, no annotations) and lack of output schema, the description achieves high completeness by specifying what the tool returns ('descriptions and pricing'). This compensates adequately for missing structured output definitions, though it could explicitly note the return type (e.g., 'returns a list').

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 has zero parameters, establishing a baseline of 4 per the scoring rubric. The description appropriately focuses on the tool's output rather than non-existent inputs, requiring no parameter-specific elaboration.

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 uses specific verb 'List' with clear resource 'tools available in the Agent Toolbelt API catalog'. It effectively distinguishes this discovery/meta-tool from the 20+ functional sibling tools (audit_dependencies, bear_vs_bull, etc.) by identifying it as the catalog listing operation.

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?

The description implies usage through the action 'List all tools' but provides no explicit when-to-use guidance, prerequisites, or alternatives. While the agent can infer this is for discovery when tool availability is unknown, the text lacks explicit guidance on when to prefer this over directly invoking known tools.

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