AnyList 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 AnyList it covers these actions: List shopping lists, Add list item, Cross off item, Read recipe, Create recipe, Add recipe to meal plan, Add meal plan ingredients to list.

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: AnyList.
`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

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-redundant traits: 'Free, no browser session' tells the agent this call has no cost and does not open or consume a browser, which materially affects how liberally it can be called. It also sketches the return contents, which is useful absent an output schema.

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 critical instruction ('Call it before the first browser step') and cost note are present and the whole thing is compact, but the opening sentence is a long comma-separated content list that delays the key point, and the AnyList action run-on is dense though justified for matching.

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-required-parameter, read-only guide tool with no output schema, the description covers trigger timing, scope across catalog and non-catalog apps, cost/session behavior, and what the returned guidance will include. Nothing an agent needs in order to decide to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it clarifies that the `app` parameter can be any web app (falling back to a general method outside the catalog) and enumerates the AnyList actions that `task` values can map to. That enumeration helps the agent phrase the task argument usefully.

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 this returns operational guidance for driving a web app through the Cloud Browser, enumerating what the guidance contains (which browser, sign-in link, step-by-step method, screens/menus/actions, notes, dedicated tools). It is clearly a knowledge/guide tool rather than an action tool, which separates it from the cotlet_browser_* and anylist_* siblings, though the leading phrase 'How to work in an app' is a content list rather than a crisp verb+resource statement.

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?

'Call it before the first browser step in an app' gives a concrete trigger point in the workflow, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets expectations for unsupported apps. There is no explicit when-not-to-call (e.g. mid-flow or after guidance is already loaded), but the timing guidance is unambiguous.

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

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