Agent Salon SF

Read a source-backed salon guide

get_guide

Read-onlyIdempotent

A build-time guide snapshot: answer, evidence rows, metrics, source dates and limits. Slugs are listed at /api/v1/guides. No live prices or availability are implied.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, so the description adds genuine context beyond them: the data is a build-time snapshot (potentially stale), it has source dates and stated limits, and it should not be read as current pricing. It stops short of saying how staleness is surfaced or what happens on an unknown slug.

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 dense sentences with no filler: the data-freshness qualifier leads, the payload contents follow, and the sourcing hint comes last. Every clause carries information an agent needs.

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?

With no output schema, the description usefully sketches the return shape (answer, evidence rows, metrics, dates, limits) and flags the snapshot/staleness constraint. It is nearly complete for a single-parameter read tool, lacking only error/not-found behavior.

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 0% and the single parameter is undocumented there beyond min/max length, so the description carries the burden — and it does point the agent to /api/v1/guides for valid slug values. It does not describe slug format conventions or lookup-failure behavior, keeping it short of full compensation.

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 names the resource (a guide snapshot) and enumerates what it returns — answer, evidence rows, metrics, source dates, limits — so an agent knows this is a static reference lookup rather than a live query. The explicit 'no live prices or availability are implied' separates it from check_availability/get_availability siblings, though the verb itself is only implied by the title.

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?

'Slugs are listed at /api/v1/guides' tells the agent how to obtain the required input before calling, which is real routing guidance. The 'no live prices or availability' caveat functions as an implicit when-not, steering live-data questions to availability siblings, but it never names those alternatives explicitly.

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

All Agent Salon SF 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?