Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fresha_venue

Use a Fresha venue slug to retrieve its profile, opening hours, full address, rating, gallery images, and grouped service menu with prices and durations.

Instructions

Get one Fresha venue's profile, opening hours and service menu. Returns one Fresha (fresha.com) venue: name, description, canonical page, country and currency, business type, full postal address with coordinates, average rating with its rating count and rating badge, published opening hours per day, gallery images and the venue's own service menu. The service menu is grouped as the venue groups it; every service carries its own retail price in the venue's own currency and its shortest and longest duration in seconds, so this is the only place this API publishes a price and it is always the provider's own menu price, never a quote or a booking price. Pass a slug from fresha-search-venues. An unknown slug is a not-found, not an empty success. No staff, professional profile, review text or reviewer identity is returned, and no availability slot, booking or checkout data exists on this route.

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

Input Schema

NameRequiredDescriptionDefault
slugYesVenue page slug, e.g. toto-hair-new-york-201-grand-street-oqiknjih

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so unusually well: it discloses error semantics ('An unknown slug is a not-found, not an empty success'), price semantics ('always the provider's own menu price, never a quote or a booking price'), and explicit absences (no staff, reviews, reviewer identity, availability, checkout). It also enumerates what is returned, substituting for the missing output schema.

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 sentence one and the remaining sentences are information-dense rather than padded. The long field-enumeration sentence reads somewhat like a dumped output schema and could be tightened, but no sentence is purely redundant.

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 fetch with no output schema and no annotations, the description covers purpose, return contents, price/duration semantics, error behavior, and scope exclusions. Nothing an agent needs in order to call it correctly or interpret the result appears to be missing.

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 100%, so the schema already documents the single slug parameter and its example format, making the baseline 3. The description adds provenance for the value (it must come from fresha-search-venues) and the failure behavior for an invalid value, which is meaningful semantics beyond the schema.

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?

The first sentence states a specific verb and resource ('Get one Fresha venue's profile, opening hours and service menu'), and the description later pins its relationship to fresha_search_venues as the slug source. An agent can distinguish this single-venue lookup from the search/landing siblings without opening any schema.

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 explicit usage context ('Pass a slug from fresha-search-venues') and a clear exclusion ('no availability slot, booking or checkout data exists on this route'), which steers an agent away from using it for booking questions. It stops short of naming the alternative tool to use for availability or staff data, so it is clear but not a complete routing rule.

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

Deploy Server

Other Tools