ChowNow MCP Server and API by Cotlet

Hide sold-out item in ChowNow

chownow_hide_sold_out_item

Read-onlyIdempotent

Hide sold-out item in the user's own ChowNow account from ChatGPT, Claude or any AI agent. Returns how to do it in ChowNow step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ChowNow Cloud Browser. ChowNow's official API: ChowNow has no API a restaurant owner can use on its own (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": "chownow_hide_sold_out_item"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, it discloses the return shape (step-by-step screens, buttons, fields) and explicitly states it performs no side effects, reinforcing readOnlyHint=true. It also supplies the underlying rationale — ChowNow has no owner-accessible API — which explains why the browser tools are required. With no output schema present, it could have gone further on the exact return structure, but the key behavioral facts are covered.

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 and the 'returns a guide, opens nothing' clarification in the first sentence. The trailing parenthetical ('checked 28 Oct 2026') and the 'from ChatGPT, Claude or any AI agent' phrase are padding that adds little for an agent, but the rest is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema guide tool, the description covers what it returns, that it has no side effects, and which tools complete the workflow. Nothing needed to invoke it correctly is missing.

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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter talk.

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?

The description opens with a specific verb and resource ('Hide sold-out item in the user's own ChowNow account') and immediately clarifies the deliverable: a step-by-step guide rather than an action. It also names the tools that actually perform the action (cotlet_browser_*), distinguishing it from the browser siblings.

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 two-step usage flow: call this to get screens/buttons/fields, then execute with cotlet_browser_* in the ChowNow Cloud Browser. It is explicit that this tool 'opens nothing by itself,' which prevents an agent from mistaking it for an executor. It does not state exclusions (e.g., when to prefer a native chownow_* mutation tool instead), which keeps it off a 5.

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

All ChowNow 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?