Skip to main content
Glama

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 Pike13 it covers these actions: Search customer records, Filter and sort customer list, View customer dashboard.

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

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Pike13.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: it costs nothing, consumes no browser session, and enumerates what the returned guidance contains. It stops short of saying whether results are cached or how large the guide is, so it is strong but not exhaustive.

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 core purpose and the call-timing instruction, with the edge-case behavior following. The middle enumeration of covered artifacts is a long, comma-heavy run-on and the Pike13 action list partly duplicates sibling tool names, which costs some density, but every clause still conveys scope information.

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 correctly assumes responsibility for describing the return contents, and it does so at the right level of abstraction. For zero required parameters and a simple guide tool this is nearly complete; only caching or repeat-call behavior for the same app is 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% and both parameters (app, task) are documented with defaults, so the baseline is already a 3. The description adds meaning the schema does not: the app value may point outside the Cotlet catalog and will still return a usable general method, which tells the agent it should not skip the call when the app looks unfamiliar.

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 states a specific resource (a per-app playbook: which browser to use, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools) and explicitly marks it as informational rather than actional ('Free, no browser session'), which separates it from the cotlet_browser_* action siblings. An agent can tell this is a lookup-and-plan tool, not a click/navigate tool, without opening the schema.

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

Usage Guidelines5/5

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

Gives a precise trigger: 'Call it before the first browser step in an app', which places it ahead of every cotlet_browser_* call. It also handles the coverage edge case ('Works for any web app; one outside Cotlet's catalog gets the general method') and names the fallback to app-specific tools 'when Cotlet has them', so routing is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources