Skip to main content
Glama

plateau-candy

get_services

Read-only

Get available consultation services from Plateau Candy. Returns event type IDs, titles and durations — call this before get_availability or book_consultation to obtain the required event_type_id.

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": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
servicesYes
booking_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description restates the read-only nature through the returned fields rather than adding safety context. The genuinely additive piece is the dependency ordering (event_type_id is required by downstream tools), while failure modes, empty-result behavior, or caching are not discussed. With annotation coverage plus an output schema present, this is adequate but not rich.

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 sentences, front-loaded with purpose and followed by the return payload and the call-ordering constraint. No filler, no repetition of the title.

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 parameterless lookup with an output schema and a readOnly annotation, nothing material is missing: the agent knows what it returns, when to call it, and which tool consumes its output.

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 the baseline is 4; the description cannot document inputs it does not have. It does usefully explain that the returned event_type_id is a required input to sibling tools, which clarifies the data flow even though it is an output rather than a parameter.

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 ('Get available consultation services from Plateau Candy') and immediately names what comes back (event type IDs, titles, durations), so an agent can distinguish it from get_availability or get_profile without opening the schema.

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?

Gives an explicit ordering rule: call this before get_availability or book_consultation to obtain the required event_type_id, and names both downstream siblings it feeds. This is exactly the when-to-use guidance an agent needs for a prerequisite lookup tool.

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