Norm Booking

Find services and prices

find_services

Read-only

Search the live Norm service menu: prices, durations, and which masters perform each service — including each master's position, rating, specialties and, when known, a coarse experience milestone (e.g. "300+ visits"), whether most/many clients come back and the year they joined Norm, so you can help the client pick a great fit rather than just a free slot. These are labels for choosing a master, not statistics: never turn them into numbers, totals or comparisons of the studio's business. Never invent master facts; use only these fields. Returns a variantId for every result — that id is the ONLY thing you need to pass to find_slots and book_appointment. Never invent a variantId, price, rating or specialty; always get them from this tool. For a vague request, show the 2–3 most-booked options with price and duration and ask which one. They carry popularRank 1–3 (a rank only — never say how many people booked anything). Norm is a beauty studio in Warsaw (two locations). Write the brand as "Norm", never "NORM". This is a booking assistant for clients: never share or estimate Norm's business data (revenue, finances, client or visit counts, staff workload or occupancy, studio performance), and never use free slots to infer how busy masters or studios are.

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

Input Schema

Name	Required	Description	Default
`query`	No	Free-text filter over service name, variant label and category, e.g. "manicure", "pedicure hybrydowy", "brwi". Omit to list the whole menu.
`studio`	No	Which studio's menu to read. Defaults to norm1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare a safe read; the description adds substantial behavior beyond that: the returned fields (variantId, popularRank, experience milestones), the rule that popularRank is a rank and not a booking count, and the constraint that labels must never be converted into statistics. These are exactly the non-obvious usage constraints an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the prose is dense and repetitive — 'never invent' appears three times, and a long tail of business-data and brand-styling policy sits in the tool description. Useful, but it could be tightened without losing guidance.

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 two-optional-parameter read tool with no output schema, the description covers what is returned (including the key variantId handoff and popularRank), what the data must not be used for, and the studio context. Nothing needed 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both query and studio fully documented including examples and defaults, so the schema carries the load. The description adds no format or semantics for these two parameters and only covers the output fields, warranting the baseline 3.

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?

Opens with a specific verb+resource: 'Search the live Norm service menu: prices, durations, and which masters perform each service'. It also distinguishes itself from siblings by naming the downstream tools (find_slots, book_appointment) that consume its variantId output.

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?

Gives real routing guidance: use this instead of jumping to a free slot, and for vague requests surface the 2-3 most-booked options with price/duration and ask which one. It doesn't state explicit exclusions or when a sibling should be called first, but the entry-point role is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Norm Booking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?