Yenta Directory

Venue profile by name

venue_profile

Read-onlyIdempotent

Get a named venue's published profile summary — give its name (and city) or slug; not every venue enables this richer profile, so if it reports the venue is not available, fall back to get_venue with the slug from search_venues (the venue's own host calls this get_venue_profile).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Disambiguate a name by city (call list_cities); ignored for a slug.
`venue`	Yes	Venue name or slug; call search_venues to discover one.

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No
`items`	No
`reason`	No
`sample`	No
`source`	No	FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:<id>`` for every read that answers from one venue, and the literal ``directory`` for the two cross-venue reads, which have no single revision to cite.
`status`	Yes
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

addedOutput schema / properties / sample

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sample"
+}

First observedSep 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: not every venue enables this richer profile, and the tool may report unavailability, which is beyond what annotations provide. It also clarifies the fallback behavior.

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?

The description is a single, dense sentence that front-loads the core purpose and then packs in usage guidance, fallback logic, and a naming hint. Every clause earns its place; no filler.

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?

Given the output schema exists, the description doesn't need to explain return values. It covers the key contextual aspects: input forms, disambiguation, availability caveat, fallback path, and sibling relationship. An agent has enough to call this tool correctly.

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 both parameters. The description adds meaning by explaining that 'venue' can be a name or slug, and that 'city' is used for disambiguation and ignored for slugs. This goes beyond the schema's basic descriptions.

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 description clearly states the tool's purpose: retrieving a named venue's published profile summary, with specific input forms (name+city or slug). It also distinguishes itself from sibling tools like get_venue and search_venues by noting the richer profile and fallback behavior.

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

Usage Guidelines5/5

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

The description explicitly provides when to use this tool (for a named venue's richer profile) and when not to (if unavailable, fall back to get_venue with slug from search_venues). It also mentions the venue's own host calls this get_venue_profile, which helps an agent understand the tool's role.

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

All Yenta 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.

Resources

Need Help?