ChowNow MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For ChowNow it covers these actions: List orders, Accept order, Hide sold-out item, Update hours, Set temporary closure, List customers.

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": "cotlet_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: ChowNow.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior; the description's real added value is "Free, no browser session," which tells the agent there is no cost or session side effect. Beyond that it adds little about behavior — no statement about whether guidance is cached or changes over time, and "works for any web app" sits slightly awkwardly against openWorldHint=false, though that reflects the static lookup rather than a true contradiction.

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 front-loaded purpose and the explicit call trigger are good, but the first sentence piles six separate content categories into one clause chain, and the closing ChowNow action list reads as appended boilerplate. It is informative but not tight.

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, the description does the necessary work of previewing what the guide returns: which browser, the sign-in link, the step-by-step method, screens, menus, actions, notes, and dedicated tools. An agent knows what it will get and when to call it; only the skip-conditions are unaddressed.

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?

Schema coverage is 100%, so the schema already defines app and task, including the ChowNow default. The description adds meaning the schema does not: it enumerates the ChowNow actions the guide covers (List orders, Accept order, Hide sold-out item, Update hours, Set temporary closure, List customers), which tells the agent what a task can realistically ask for.

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 states a specific resource: guidance on how to operate an app in the user's Cloud Browser with Cotlet's browser tools, including which browser to use, the sign-in link, the step-by-step method, and screens/menus/actions. This clearly separates it from the cotlet_browser_* action tools and from the chownow_* dedicated tools, though the opening sentence is a dense run-on that takes work to parse.

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 an explicit call point: "Call it before the first browser step in an app." It also scopes coverage (works for any web app; apps outside Cotlet's catalog get the general method) and flags that dedicated tools exist for some apps. It does not say when the guide can be skipped, e.g. when calling chownow_* tools directly.

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?