Skip to main content
Glama

list_services

Read-only

Lists every Glitter Agent Gate tool with endpoints, parameters, examples, and per-call prices in XRP, RLUSD, and USDC, helping you choose a service slug for call_paid_service.

Instructions

List every Glitter Agent Gate tool with its endpoints, parameters, examples and per-call prices in XRP, RLUSD and USDC. Free: makes no payment and needs no wallet. Use this first to pick a service slug for call_paid_service.

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 observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavior the annotations do not: that the call is free, requires no wallet, and no payment is made — meaningful context that prevents an agent from hesitating over cost or auth. It does not mention pagination or output size limits, which is a minor remaining gap.

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, each doing distinct work: what is returned, what it costs, and when to use it. The decision-relevant point ('Use this first') is placed before the alternative is named, so nothing is 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?

With zero parameters and no output schema, the description must carry the return-content burden alone, and it does by enumerating endpoints, parameters, examples and per-call prices in XRP, RLUSD and USDC. Nothing an agent needs in order to call this correctly and act on the result is missing.

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 nothing for the description to disambiguate; baseline applies. The description correctly spends no words on parameter semantics and instead describes the payload contents.

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 opens with a specific verb and resource ('List every Glitter Agent Gate tool') and enumerates the returned fields (endpoints, parameters, examples, prices in three currencies), so the agent knows exactly what this returns. It also implicitly distinguishes itself from the paid call tools by being the free catalog lookup.

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

Usage Guidelines5/5

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

It gives an explicit sequencing instruction — 'Use this first to pick a service slug for call_paid_service' — naming the sibling that consumes the output and the exact field needed. It also states the cost condition ('Free: makes no payment and needs no wallet'), which tells the agent when this tool is the safe choice over a paid call.

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