Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

justeat_restaurant

Retrieve a Just Eat restaurant by its unique_name slug to get address, cuisine, rating, and active order status. Use it to check details or order availability from a search result.

Instructions

Get one Just Eat restaurant's detail. Returns one Just Eat restaurant by unique_name, the slug found in a search result. The response has the restaurant id, name, address, city, postal code, country, image, primary cuisine, rating and rating count, and is_active, which says whether it currently accepts orders. rating can read 0 even when the site shows one. An unknown unique_name returns 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unique_nameYesRestaurant slug, from a search response's unique_name field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it enumerates the returned fields, flags the `rating` = 0 edge case, and states that an unknown `unique_name` yields a 404. It stops short of an explicit read-only statement or any rate-limit/auth context, but the disclosure is rich for a read tool.

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?

Front-loaded with the action, then return contents, then edge cases, in a compact four-sentence block. Minor redundancy between 'Get one Just Eat restaurant's detail' and 'Returns one Just Eat restaurant by `unique_name`', but every sentence otherwise earns its place.

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 and no annotations, the description usefully compensates by listing the returned fields and the two notable edge cases (rating 0, 404 on unknown slug). It is complete enough to call correctly; only authentication or error-shape details are absent.

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%, so the single parameter is already documented in the schema, and the description largely echoes it. The phrase 'the slug found in a search result' slightly reinforces the source of the value, but adds no new syntax or format detail 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?

Specific verb ('Get') plus a precisely scoped resource ('one Just Eat restaurant's detail') and the exact key that selects it (`unique_name`). It is easily distinguished from siblings like justeat_search and justeat_restaurant_menu.

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

Usage Guidelines3/5

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

The description implies the call sequence by noting `unique_name` is 'the slug found in a search result', which hints that justeat_search precedes it. However, it never explicitly says when to use this vs justeat_search or justeat_restaurant_menu, so guidance is only implied.

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