Yenta Directory

Get destination

get_destination

Read-onlyIdempotent

Get one published destination's summary and live mcp_endpoint by its slug — always available for any published destination, so use this if destination_overview reports it is not available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`destination_slug`	Yes	The destination's slug, as returned by search_destinations.

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.4/5.0

Behavior4/5

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

Annotations already mark readOnly, idempotent, and non-destructive; the description contributes an availability guarantee and tells the agent the response includes a live mcp_endpoint. It does not cover error behavior or rate limits, but those are less critical for a simple read with a safety profile.

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?

Single sentence with the key scoping phrase front-loaded before the routing guidance. No filler or repeated annotations.

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 one-parameter, read-only tool with an output schema, the description covers how to identify the destination, what to expect in the result, and when to prefer it over destination_overview. The only light gap is that 'live mcp_endpoint' is domain jargon, but the output schema presumably defines it.

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?

The schema describes the only parameter (destination_slug) as 'as returned by search_destinations', and the description essentially repeats 'by its slug'. Schema coverage is 100%, so no additional parameter semantics are needed; the description adds no new constraint or format detail.

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?

States a precise action ('get') and specific resource ('one published destination's summary and live mcp_endpoint'), keyed by slug. The phrase 'use this if destination_overview reports it is not available' distinguishes it from the most similar sibling.

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?

Explicitly frames when to use: 'always available for any published destination', and points to the alternative destination_overview when that tool reports non-availability. It does not list exclusion cases, but for a simple read the guidance is clear.

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?