Skip to main content
Glama

uPlanny — салоны и запись

Карточка салона

get_salon
Read-onlyIdempotent

A salon's public card by slug: address, coordinates, time zone, rating, categories, description, masters with ratings and every service with price, duration, rating and masters.

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_salon"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSalon slug from search results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by spelling out the richness of the returned object, which matters because no output schema exists, but it says nothing about behavior for an unknown slug, payload size, or rate limits.

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?

A single front-loaded sentence that immediately anchors on the resource and scope before listing contents. It is dense but nearly every clause earns its place, with only mild redundancy in 'masters with ratings ... and masters' at the end of the service list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup with no output schema, the description compensates well by enumerating the fields the card returns. The remaining gap — not-found behavior and the absent-sibling guidance — is modest for a tool this simple.

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?

Only one parameter, and the schema already documents it at 100% coverage as 'Salon slug from search results'. The description's 'by slug' restates rather than extends that meaning, so the schema is doing the heavy lifting — the baseline 3 for full coverage 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?

States a specific resource retrieval — a salon's public card looked up by slug — and enumerates the payload (address, coordinates, time zone, rating, categories, description, masters, services with price/duration). An agent can tell this is the detail-lookup counterpart to search_salons, though it never names that sibling to make the contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as search_salons. The phrase 'by slug' plus the schema note 'Salon slug from search results' only weakly implies this is a follow-up call after a search, leaving the routing decision to inference.

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