Skip to main content
Glama
Sign In

Foodly

by solutions.foodly
OverviewDiscussionsAdmin

Free table times

get_table_times
Read-onlyIdempotent

The times a Foodly restaurant has free for a table on one day, in the restaurant's local time. Booking is done in the Foodly app and the restaurant confirms it.

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": {
      "restaurant_id": "<restaurant_id>",
      "date": "<date>"
    },
    "name": "get_table_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe day, as YYYY-MM-DD, in the restaurant's calendar.
party_sizeNoHow many people. With it, times without room for the group show as full.
restaurant_idYesThe restaurant id from find_restaurants.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, and closed-world behavior. The description adds that times are in the restaurant's local time and that booking happens in the Foodly app with restaurant confirmation, which is useful context, but it does not describe return shape or whether availability is live.

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?

The description is two short sentences and front-loads the returned resource. The booking sentence is useful context, though it is not strictly invocation-critical.

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 simple three-parameter read-only tool with full schema coverage and no output schema, the description is mostly complete: it states the resource, scope, local-time behavior, and that booking happens elsewhere. It could be stronger with sibling routing guidance and a hint about the returned time structure.

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 the schema already explains restaurant_id, date, and party_size. The description adds only local-time framing, which is already reflected in the date parameter description, and adds no new parameter-specific semantics.

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?

The description names a specific resource, free table times, and scopes it to one Foodly restaurant and one day in local time. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings such as get_restaurant or find_restaurants.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The booking note gives workflow context but does not tell an agent when this availability lookup is the right choice.

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

All Foodly toolsInspect
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