tl;dv 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 tl;dv it covers these actions: List meetings, Get transcript, Create clip, Add note, Share meeting, Add meeting to folder.

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: tl;dv.
`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

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: 'Free, no browser session' — i.e., it consumes no browser session and incurs no cost, which matters for an agent deciding whether to call it. It also discloses that it can surface the app's dedicated tools when they exist, but does not describe response shape beyond the content list.

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?

Purpose and the 'call before first browser step' trigger are front-loaded, and the trailing tl;dv action enumeration is useful scoping rather than filler. The first sentence is a long run-on that packs several ideas together, which slightly hurts scannability but wastes no content.

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 bears the burden of telling the agent what comes back, and it does: browser selection, sign-in link, method, screens/menus/actions, notes, and dedicated tools. What is missing is any hint about length or format of the returned guidance and how the `task` input changes it, a minor gap for a two-parameter read-only tool.

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 description coverage is 100% and both parameters document their defaults (app defaults to tl;dv, task is the user's own words), so the schema carries the semantics. The description adds only indirect meaning via the tl;dv action list, which hints at what the `app` value unlocks, but says nothing extra about how `task` shapes the output.

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 description uses a specific verb+resource framing ('How to work in an app... with Cotlet's browser tools') and enumerates the returned content (browser choice, sign-in link, step-by-step method, screens, menus, actions, notes, dedicated tools). It is clearly a guidance/knowledge tool rather than an action tool, which separates it from the cotlet_browser_* siblings, though it never names a sibling 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?

It gives a concrete trigger: '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 does not state when to skip it or point to a specific alternative, so it stops short of full routing guidance.

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

All tl;dv 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?