Manatal 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 Manatal it covers these actions: Search candidates, Create candidate, Add candidate to job, Move candidate to stage, Drop candidate with reason, Add candidate note, List job pipeline.

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: Manatal.
`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 establish this is a read-only, idempotent, non-destructive, closed-world call. The description adds value beyond that by saying it is free and requires no browser session, which matters for a tool an agent may call repeatedly before acting. It does not describe output length or how the guide is structured in the response, though the content list partially covers that.

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 trigger to call it early is front-loaded in the opening sentence, and the short follow-on sentences carry distinct facts (cost, session requirement, catalog fallback, Manatal action coverage). The opening sentence is a dense run-on list of guide contents, but it is not padded.

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 and only annotations for safety, the description explains what the guide returns and the no-cost/no-session constraints, which is what an agent needs to decide to call it. The enumerated Manatal actions make the coverage boundary explicit; the remaining gap is how to fall back when an app is not in the catalog beyond the general method.

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% and both parameters (app name/slug with a Manatal default, and the user's task in their own words) are already documented in the schema. The description adds only indirect meaning about how those inputs shape the guide, so the baseline of 3 applies.

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?

States a specific resource and scope: a per-app guide covering which browser/sign-in link to use, the step-by-step method, screens, menus, actions, notes, and the app's dedicated tools. That is concrete enough to separate it from the cotlet_browser_* primitives and the manatal_* action tools.

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, and "works for any web app; one outside Cotlet's catalog gets the general method" sets expectations for unknown apps. It hints that dedicated app tools exist but stops short of an explicit "prefer manatal_* tools over manual clicking when available" routing rule.

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

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