Skip to main content
Glama

Bookipi 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 Bookipi it covers these actions: Filter invoice lists and view archived invoices, Review customer correspondence and transaction history, View or download an eSign audit trail.

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: Bookipi.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 non-open-world, so the safety profile is covered. The description adds value the annotations cannot: that the call is free, opens no browser session, and returns a general method for unlisted apps instead of failing. It does not describe the shape or size of the returned guidance.

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 trigger instruction is front-loaded, but the opening is a single long run-on sentence with a trailing catalog of Bookipi actions that reads as bulk rather than routing information. It is informative yet noticeably heavier than needed for a two-parameter lookup tool.

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?

There is no output schema, so the description must disclose return contents, and it does so by enumerating browser choice, sign-in link, method steps, screens/menus/actions, notes and dedicated tools. Combined with the no-session and fallback notes, an agent has enough to call it correctly and act on the result.

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

Parameters3/5

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

Schema coverage is 100%, so both 'app' and 'task' are already documented in the schema, including the Bookipi default. The description adds only marginal meaning by listing the Bookipi actions the guide covers and clarifying the outside-catalog fallback; it gives no guidance on how 'task' shapes the returned method.

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 definition names a specific resource (an app-specific how-to guide) and enumerates its contents: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It implicitly separates itself from the cotlet_browser_* siblings by noting it is a guide that is 'called before the first browser step' rather than a browser action, though it never names an alternative tool explicitly.

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 clear trigger condition, and 'works for any web app' plus the fallback for apps outside the catalog tells the agent it is safe to call broadly. It stops short of stating when-not to use it or naming the follow-up tools by name.

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