Skip to main content
Glama

List salons

list_salons

Use collection=public-research for public-source profiles with menus, add-ons, stylist information and policies; get_merchant returns the full public_research object. Salons covered (San Francisco), ordered profiled, detailed, then listed, with depth, neighborhood, price floor and range, stylist count, availability basis and freshness, last_verified_at and verification date. Paginated: limit (default 50, max 200), offset, depth=profiled|detailed|listed.

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

Input Schema

NameRequiredDescriptionDefault
depthNoprofiled = booking-system depth; detailed = priced menu + booking link + hours or durations; listed = the rest
limitNo
offsetNo
collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / collection
      Added value: +{
      +  "const": "public-research",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the ordering (profiled, detailed, then listed), pagination limits and the fields surfaced (neighborhood, price floor/range, stylist count, freshness, last_verified_at). It says nothing about authentication, rate limits or what an empty/failed result looks like, so the behavioral picture is incomplete for a tool with zero annotation coverage.

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

Conciseness2/5

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

The description opens with a usage note about a const parameter instead of stating what the tool does, and the middle sentence is a dense run-on string of attributes. Information density is high but the front-loading and readability are poor, forcing the agent to parse before it knows the tool's purpose.

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 four-parameter, read-only-style listing tool with no output schema and no annotations, the description covers region, ordering, returned fields and pagination defaults. Only permission/auth context and result-envelope details are missing, which is a minor gap.

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?

Schema coverage is only 25% (only depth is documented in the schema), yet the description supplies the limit default of 50 and max of 200, the collection const value and the depth enum meaning. Only offset is left without added semantics, which is acceptable for a conventional paging parameter.

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?

It identifies the resource (salons), the region covered (San Francisco) and the depth tiers, and it names get_merchant as the way to get the full public_research object. The verb 'list' is only implied by the name and the ordering/pagination language rather than stated outright, but an agent can tell it apart from get_salon and get_merchant.

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?

'Use collection=public-research for public-source profiles...' and the pointer to get_merchant give partial routing guidance, but get_salon, get_stylist and search_merchants are never mentioned, so the choice between listing and fetching a single salon or stylist is left 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