Skip to main content
Glama

get_services

Read-onlyIdempotent

Get detailed service list for an operator.

Returns id, name, description, price_isk, type, and max_guests for each service.
Provider-backed lodging also returns unit_kind and units. When unit_kind is
``bed``, describe it with unit_description verbatim and never call it a room.
Use the returned service_id in check_availability, get_price_quote, and create_booking.

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": {
      "operator_id": "<operator_id>"
    },
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it enumerates returned fields, discloses a conditional shape (provider-backed lodging returns unit_kind and units), and gives a naming rule for the 'bed' case, which is behavioral guidance not present in structured fields.

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?

The purpose is front-loaded in the first sentence, followed by return fields and then workflow guidance, which is a sensible order. The 'never call it a room' clause is slightly idiosyncratic but earns its place as a correctness rule.

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 single-parameter read tool with an output schema and full annotation coverage, the description covers purpose, return shape, a conditional edge case, and downstream usage. Nothing an agent needs to invoke it correctly 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?

Schema coverage is 100% and the single operator_id parameter is fully documented in the schema, including the 'obtain from search_operators, do not guess' instruction. The description adds no parameter-level detail, so 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?

The description opens with a specific verb and resource ('Get detailed service list for an operator'), which is unambiguous and lets an agent distinguish this listing tool from the booking/quote/availability siblings. It stops short of naming a contrasting sibling, but no sibling appears to overlap this purpose.

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?

It gives clear downstream context: the returned service_id feeds check_availability, get_price_quote, and create_booking, which tells the agent where this tool sits in the workflow. It does not state explicit when-not-to-use conditions, but the usage context is concrete rather than implied.

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