Skip to main content
Glama
Sign In

Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: test an automation script

cotlet_automation_test

Runs a script once now in a hidden tab of the user's Cloud Browser with every write skipped, and answers its status, rows, log, steps and credits. Uses browser minutes. Test the exact script you will save. automation: test against that automation's seen rows and state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script": "<script>"
    },
    "name": "cotlet_automation_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptYesThe Python script: `def run(ctx):` with the cotlet SDK (see the guide).
automationNoThe automation's id from cotlet_automation_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: hidden tab, all writes skipped (a dry-run semantic the readOnlyHint=false / destructiveHint=false pair does not convey), consumption of browser minutes (a cost warning), and an enumeration of what the response contains. An agent knows the side-effect profile and the price before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and its scope, followed by the return/cost clause and the parameter note. No filler and nothing repeated from the schema or annotations.

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?

With no output schema, the description supplies the return surface (status, rows, log, steps, credits), and with only two fully-documented parameters there is little left unsaid. Cost and dry-run behavior are the two things an agent most needs here, and both are covered.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by explaining that `automation` makes the test run against that automation's seen rows and state, which is a meaningful semantic the schema field text does not give. The `script` parameter gets no extra meaning beyond 'the exact script you will save'.

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 verb and resource ('Runs a script once now in a hidden tab of the user's Cloud Browser') plus the exact execution scope ('every write skipped') and the returned artifacts. It is clearly distinguishable from cotlet_automation_save and the cotlet_browser_* primitives.

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?

'Test the exact script you will save' establishes the when-to-use condition (dry run before persisting), and the `automation` sentence distinguishes the two testing modes. It stops short of naming cotlet_automation_save explicitly or stating when not to use this tool (e.g. when a real run is needed).

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

All 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