Cronometer MCP Server and API by Cotlet

Add note in Cronometer

cronometer_add_note

Read-onlyIdempotent

Add note in the user's own Cronometer account from ChatGPT, Claude or any AI agent. Returns how to do it in Cronometer step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Cronometer Cloud Browser. Cronometer's official API: Cronometer has no public API (checked 5 Nov 2026).

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": "cronometer_add_note"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', so there is no contradiction. It adds real value by describing the return shape (screens, buttons, fields) and the required downstream browser workflow. It does not state prerequisites such as needing a browser session already open first.

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 key constraint (returns instructions, does not act) is front-loaded, which is good. However, 'from ChatGPT, Claude or any AI agent' is filler and the dated 'checked 5 Nov 2026' aside is noise that does not help an agent decide or invoke.

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 zero-parameter, no-output-schema tool, the description covers what is returned and what must happen next. The main omission is session prerequisites for the cotlet_browser_* step, which an agent may need in order to sequence calls correctly.

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?

The tool takes zero parameters and the schema is closed, so there is nothing for the description to disambiguate. Baseline of 4 applies for a parameterless tool.

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?

States a specific verb and resource (add a note in the user's Cronometer account) but immediately reframes the behavior: the tool returns step-by-step instructions rather than performing the write. That clarification prevents a serious misread, though the name/behavior tension costs a point versus a cleanly scoped definition.

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?

Gives an explicit follow-up path: take the returned instructions and execute them with cotlet_browser_* tools in the user's Cronometer Cloud Browser. It also rules out an API route by noting Cronometer has no public API. It does not name alternatives among the cronometer_* siblings, but the when-to-use context is clear.

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

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