Yemekhost Restoran Bul

Get a restaurant branch

get_restaurant

Read-onlyIdempotent

Reads one listed branch and the other listed branches of its brand. Identify it by the three slugs a search result carries: tenantSlug, brandSlug and branchSlug. Orders are not placed here: every result carries an orderUrl, the restaurant's own page, where the person places the order.

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": {
      "tenant_slug": "<tenant_slug>",
      "brand_slug": "<brand_slug>",
      "branch_slug": "<branch_slug>"
    },
    "name": "get_restaurant"
  }
}

Input Schema

Name	Required	Description
`latitude`	No	Optional position, to get distances and whether the branch delivers there.
`longitude`	No	Optional position; give it together with latitude.
`brand_slug`	Yes	The brandSlug of the search result.
`branch_slug`	Yes	The branchSlug of the search result.
`tenant_slug`	Yes	The tenantSlug of the search result.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior beyond that: the response includes the brand's other branches, and every result carries an orderUrl pointing at the restaurant's own ordering page. It does not mention pagination or how many sibling branches come back, which is the only notable gap.

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 short sentences, each doing distinct work: what is read, how to identify it, and where ordering happens instead. The scope and the identifying keys are front-loaded with no filler or repetition.

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 partially compensates by describing what comes back (the branch plus the brand's other branches, each with an orderUrl). Combined with full schema coverage and read-only annotations, an agent has what it needs to call this correctly; only return-shape details like counts or field names remain unstated.

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 description coverage is 100%, so all five parameters, including the optional latitude/longitude distance behavior, are already documented. The description adds provenance for the three required slugs (they come from a search result), which mildly reinforces the schema rather than extending it. Baseline 3 applies when the schema carries the parameter burden.

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?

"Reads one listed branch and the other listed branches of its brand" gives a specific verb and a precisely scoped resource, including the extra return scope (sibling branches of the brand). It implicitly distinguishes itself from the search/list siblings by requiring slugs carried by a search result, but it never names an alternative tool, so differentiation is inferred rather than stated.

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?

The description establishes the precondition clearly: you need the three slugs a search result carries, which frames this as a follow-up lookup after searching. It also gives an explicit exclusion — orders are not placed here, use the orderUrl — but offers no direct comparison to search_restaurants or list_places for the case where the user has not searched yet.

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

All Yemekhost Restoran Bul 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?