Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

list services

list_services
Read-only

What can this server do? Lists every tool, its price, which ones are free, and how x402 payment works. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes a safe read, but the description adds genuinely new behavioral context: the call costs nothing ('Free'), and the response explains the x402 payment mechanism so the agent learns how paid tools are billed. It does not describe response format or ordering, which keeps it short of a 5.

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?

Two short sentences, front-loaded with the purpose and ending with the cost signal. The opening question is mildly redundant with the list that follows it, but nothing is padded or buried.

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 zero-parameter, read-only discovery tool with no output schema, the description supplies exactly what an agent needs: the categories of content returned, including pricing and free-tier status, plus the payment-model explanation. Nothing material is missing for correct invocation.

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 there is no parameter meaning for the description to add; the schema is empty by design and coverage is 100%. The baseline of 4 applies with no gaps attributable to the description.

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 states a specific verb (lists) and a precise set of resources returned: every tool, its price, which are free, and how x402 payment works. That is enough for an agent to distinguish this catalog/discovery endpoint from every sibling, which are all individual data-fetching tools.

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 framing question 'What can this server do?' implies the tool is a discovery entry point, and 'Free' signals there is no cost barrier to calling it. However, there is no explicit guidance on when to call it (e.g., before choosing a paid tool) or any stated exclusion relative to the sibling tools.

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