Skip to main content
Glama

AgentSupply

List AgentSupply services

list_services
Read-only

List all services with status (live = callable now, pilot = request-only), indicative pricing and how to use them.

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
categoryNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. With no output schema, the description usefully discloses the shape of each result and defines status semantics (live = callable now, pilot = request-only); however it does not describe ordering, pagination, or how to follow up on a pilot service.

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?

One dense sentence with no filler, and the returned payload is front-loaded before the status definition. The trailing phrase "how to use them" is slightly abstract but earns its place as a summary of the usage field.

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 simple read-only, single-optional-parameter listing tool with no output schema, the definition covers purpose, returned fields, and status vocabulary adequately. The main missing piece is guidance on what to do after seeing a pilot entry (submit_request vs get_service).

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 coverage is 100% with a single optional enum parameter already documented in the schema. The description never mentions the category filter, so it adds no meaning beyond the structured field — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List all services") and enumerates what each entry carries: status, indicative pricing, and usage guidance. This distinguishes it from get_service, which returns a single service, though the sibling is never named explicitly.

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 discovery-oriented phrasing and the parenthetical defining status values, which tells an agent when an entry is actionable. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative such as get_service for detail lookup.

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