Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wendys_time_slots

Retrieve available mobile-order pickup time slots for a specific Wendy's store by its numeric store ID. Returns real check-in times to schedule arrival, separate from open/close hours.

Instructions

Get one Wendy's restaurant's available mobile-order time slots. Returns one restaurant's available mobile-order arrival ("check-in") time slots -- the times a caller can schedule a mobile pickup order for, distinct from the restaurant's general open/close hours (GET /wendys/restaurant, /wendys/store). A request with just a store id returns real available slots, no session or account required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesNumeric store id, e.g. from /wendys/nearby's stores[].store_id or /wendys/restaurant's store_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose a meaningful trait: a request with just a store id returns real availability with no session or account required. It doesn't cover rate limits, timezone handling, or empty-result behavior, but the auth/session disclosure is a genuine addition.

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-loads the core action in the first sentence, then adds the disambiguation. Slightly redundant phrasing between the first and second sentences about 'available mobile-order arrival time slots', but no filler that obscures meaning.

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 single-parameter read tool with no output schema, the definition covers what is returned, the distinction from hours endpoints, and that no auth is needed. Return-shape details (time format, slot granularity) are the only notable gap.

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% and the single store_id param is fully documented in the schema, so baseline 3 applies. The description reinforces that a bare store id suffices but adds no format or sourcing detail beyond the schema's own description.

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 specific verb and resource: retrieving one Wendy's restaurant's available mobile-order arrival time slots. It explicitly differentiates these slots from the restaurant's general open/close hours returned by /wendys/restaurant and /wendys/store, so an agent can distinguish it from the nearby sibling tools.

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?

It gives clear context for when this is the right call (scheduling a mobile pickup order) and contrasts the result with the general-hours endpoints, which routes the agent away from using those for availability. It stops short of explicit when-not conditions or naming a preferred alternative call order.

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