Skip to main content
Glama

NextUp Walk-in

Get services

get_services
Read-onlyIdempotent

The services a place offers publicly, with the prices and lengths it shows to customers (up to 30). Use a service's id with available_times, join_link or booking_link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe place's slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the description's added context is where the credit lies: it discloses that only publicly visible services are returned and that results are capped at 30. It does not say whether the 30-item cap truncates silently or how to retrieve beyond it, which keeps it out of 5 territory.

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 short sentences, front-loaded with what is returned and followed by what to do with the ids. Every clause carries information and nothing is repeated from the schema or annotations.

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 one-parameter read tool with no output schema, the description covers the shape of the return (services, prices, lengths), the result cap, and the downstream id usage. Nothing an agent needs in order to call it and use its output is missing.

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?

With schema description coverage at 100% and a single required 'slug', the schema already documents the parameter fully. The description says only that the services belong to 'a place', adding a light framing of what the slug identifies but no format or resolution detail. 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?

The description names a specific resource and its scope: the public services a place offers, including prices and durations, capped at 30. It is a noun phrase rather than a verb+resource statement, but an agent can still tell exactly what comes back and how it differs from get_place.

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?

There is no explicit when-to-use or when-not statement, and no comparison to get_place. What is offered is chaining guidance — pass a service's id to available_times, join_link, or booking_link — which is useful context but not a usage rule for this tool itself.

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