valet-parking-directory

Get Operator Profile

valet_get_operator

Read-onlyIdempotent

Get the full operator profile by slug including address, phone, listing URL, website (paid listings only), services, venues_served, FAQs, and tipping note. Use this when an agent has a slug from a search tool or directory URL and needs the profile. Returns isError on slug 404 or upstream outage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Canonical kebab-case operator slug (e.g. '12-oaks-parking-llc'). Lowercase letters, digits, hyphens only.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	Yes	TOOL-11 ToS and attribution block
`operator`	Yes	The full merged operator profile (Typesense + Payload long-tail fields)
`data_freshness`	Yes	TOOL-10 freshness stamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 28, 2026

addedOutput schema / properties / operator / properties / listing_url

Added value: +{
+  "description": "Get Valet Parking profile URL for this operator with ?ref=mcp UTM stamp (TOOL-12); present on every tier",
+  "type": "string"
+}

changedOutput schema / properties / operator / properties / website / description

Previous value: -"Operator website URL with ?ref=mcp UTM stamp (TOOL-12); null if none"New value: +"Operator's own website with ?ref=mcp UTM stamp (TOOL-12). Paid and custom listings only; null on free listings and when none is set"

changedOutput schema / properties / operator / required

Previous value: -[
-  "id",
-  "name",
-  "slug",
-  "primary_city_name",
-  "primary_state_name",
-  "primary_city_slug",
-  "primary_state_slug",
-  "service_area_city_slugs",
-  "service_area_count",
-  "services",
-  "tier",
-  "verified",
-  "claimed",
-  "phone",
-  "description_text",
-  "photo_url",
-  "address",
-  "website",
-  "venues_served",
-  "faqs",
-  "buyer_question_phrasings"
-]New value: +[
+  "id",
+  "name",
+  "slug",
+  "primary_city_name",
+  "primary_state_name",
+  "primary_city_slug",
+  "primary_state_slug",
+  "service_area_city_slugs",
+  "service_area_count",
+  "services",
+  "tier",
+  "verified",
+  "claimed",
+  "phone",
+  "description_text",
+  "photo_url",
+  "address",
+  "website",
+  "listing_url",
+  "venues_served",
+  "faqs",
+  "buyer_question_phrasings"
+]

First observedJun 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context beyond them: website is returned only for paid listings, and the tool returns isError on slug 404 or upstream outage. It does not disclose return shape, but the output schema covers that.

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?

Three sentences, front-loaded with the payload, then the when-to-use condition, then error behavior. No filler; every sentence carries distinct information.

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?

An output schema exists, so return values need not be re-explained, and the description still adds the paid-listing gate and failure modes. What remains is minor: no mention of pagination or rate limits, though for a single-item slug lookup that is low risk.

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%, and the schema already documents the kebab-case slug format with an example. The description only implies provenance ('slug from a search tool or directory URL'), which is more usage guidance than parameter semantics, so the baseline 3 applies.

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?

Specific verb+resource ('Get the full operator profile by slug') with an enumerated payload scope. It clearly distinguishes itself from the sibling find/search tools, which produce slugs rather than consume them.

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?

Explicitly states the triggering condition: 'Use this when an agent has a slug from a search tool or directory URL and needs the profile.' That routes the agent from the search siblings, though it does not name a specific alternative or state what to do when no slug is available.

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

All valet-parking-directory 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.