Skip to main content
Glama
Sign In

Lichess MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Lichess it covers these actions: Accept team join request, Send team update, Create Arena tournament, Create broadcast, Import PGN to study, Export games.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: 'Free, no browser session,' which tells the agent this call costs nothing and does not open a session — useful for planning.

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 purpose is front-loaded, but the opening sentence is a long run-on list of deliverables, and the trailing Lichess action enumeration is bulky. Every clause is informative, yet the structure could be tightened into shorter sentences without losing content.

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?

There is no output schema, so the description must explain what comes back — and it does, itemizing browser choice, sign-in link, method, screens/menus/actions, notes, and dedicated tools. For a two-parameter read-only guidance tool, nothing an agent needs is missing.

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 are documented with defaults, so the schema carries the load. The description reinforces the app scope ('For Lichess it covers these actions...') but adds no syntax or format detail beyond what the schema already states.

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 names a specific resource (guidance for working in an app) and enumerates exactly what it returns: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It is clearly distinguishable from the cotlet_browser_* primitives and the lichess_* action tools it references.

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?

It gives explicit timing guidance: 'Call it before the first browser step in an app,' and clarifies coverage ('Works for any web app; one outside Cotlet's catalog gets the general method'). It also points to the app's dedicated tools when they exist, though it does not state an explicit when-not-to-use condition.

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

All Lichess MCP Server and API by Cotlet toolsInspect
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