Okendo 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 Okendo it covers these actions: List pending reviews, Publish review, Reject review, Reply to review, Answer product question, Get product performance.

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: Okendo.
`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?

Adds behavior the annotations don't carry: it is free, consumes no browser session, and always returns a usable general method even for uncatalogued apps. It also discloses that it supplies the sign-in link and workspace browser, which explains prerequisites for later browser steps. Missing only a statement of what the returned content looks like (prose instructions vs. structured steps).

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?

Dense and largely waste-free, with no repeated annotation restatements. The key call-to-action ("Call it before the first browser step") arrives mid-sentence after a long opening clause enumerating contents, so front-loading the trigger would improve scanability.

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?

For a read-only, zero-required-parameter, no-output-schema tool, the definition covers trigger, scope, cost, and content. The only real gap for an agent is not knowing whether the result is free-form guidance to interpret or a rigid checklist to follow.

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 parameters are already documented, including the Okendo default. The description adds modest value by enumerating the Okendo actions the guide covers, which effectively defines the vocabulary for the task parameter, but it says nothing about how app names/slugs are resolved or how a vague task description is handled. Baseline 3 with a slight lift is appropriate.

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?

Uses a specific verb and resource — a guide on how to work in an app via the user's Cloud Browser with Cotlet's browser tools — and enumerates what the guide contains (browser choice, sign-in link, step-by-step method, screens/menus/actions, dedicated tools). This clearly distinguishes it from the sibling action tools (cotlet_browser_*, okendo_*), which perform steps rather than explain them.

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 explicit timing, and "Works for any web app; one outside Cotlet's catalog gets the general method" defines scope. It hints at preferring the app's dedicated tools when they exist but never states a precedence rule, so the agent must infer whether to read the guide or call okendo_reply_to_review directly.

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

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