Toast MCP Server and API by Cotlet

List time entries in Toast

toast_list_time_entries

Read-onlyIdempotent

List time entries in the user's own Toast account from ChatGPT, Claude or any AI agent. Returns how to do it in Toast step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Toast Cloud Browser. Toast's official API: Toast has an API, but the access a restaurant creates for itself is read-only (checked 28 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toast_list_time_entries"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The key disclosure, that it 'opens nothing by itself' and returns instructions only, goes beyond the readOnly/idempotent annotations and is genuinely useful. The API note (self-created access is read-only) also explains why a browser path is needed. However, the parenthetical '(checked 28 Oct 2026)' is a future-dated provenance claim that reads oddly and cannot be verified, and no detail is given about the shape or length of the returned steps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The corrective 'returns how to do it... and opens nothing by itself' is well front-loaded, but the opening clause 'from ChatGPT, Claude or any AI agent' is marketing filler, and the final API sentence with the dated check is dense and marginal.

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 parameters, no output schema, and annotations already covering the safety profile, the description supplies what an agent actually needs: what comes back (screens, buttons, fields) and which sibling tool family executes it. It is slightly incomplete in not clarifying its relationship to cotlet_app_guide.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No argument-level meaning is missing.

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 clarifies that despite the name, the tool returns step-by-step Toast UI instructions rather than data, and that it must be followed by cotlet_browser_* calls. That is a specific, non-obvious purpose, but it never distinguishes itself from the sibling cotlet_app_guide, which plausibly does something similar.

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 a clear sequence: call this to get the steps, then replay them with the cotlet_browser_* tools in the user's Toast Cloud Browser. It stops short of stating when a caller should skip this and go straight to another guide tool, or what to do if the user has no Toast Cloud Browser session.

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

All Toast MCP Server and API by Cotlet 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?