Skip to main content
Glama

List services

list_services
Read-onlyIdempotent

List the services escorts can offer on EscortFox. Returns each service's slug and English name (e.g. "massage" = Massage). Use a slug as service in search_listings to find escorts who offer it; services apply to escort searches only.

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

Output Schema

NameRequiredDescriptionDefault
servicesYesThe service vocabulary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "services": {
      +      "description": "The service vocabulary.",
      +      "items": {
      +        "properties": {
      +          "name": {
      +            "description": "English name.",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "Service slug, for `service`.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "services"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds value beyond that by disclosing the returned fields (slug plus English name) and the domain limitation that services only apply to escort searches, which the annotations do not convey.

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?

Two tight sentences with the purpose front-loaded, followed by the downstream usage rule. There is no redundant restatement of the title and no filler.

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?

This is a simple zero-argument lookup with an output schema and full annotation coverage; the description supplies the one thing that matters, the slug-to-name mapping and its downstream consumer. Nothing an agent needs in order 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.

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 semantics to explain and the baseline is 4. The description correctly avoids inventing inputs and instead documents the output vocabulary an agent will pass into search_listings.

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?

States a specific verb and resource ('List the services escorts can offer on EscortFox') and immediately specifies the shape of the result ('each service's slug and English name') with a concrete example. An agent can distinguish this reference-list tool from search_listings, list_cities, and get_listing without opening a schema.

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?

Explicitly says how to use the result ('Use a slug as `service` in search_listings') and constrains scope ('services apply to escort searches only'), which prevents misuse in city/country lookups. It stops short of naming a when-not-to-call alternative for other reference lists, but the context is clear.

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