Exact Online MCP Server and API by Cotlet

Book journal entry in Exact Online

exact_online_book_journal_entry

Read-onlyIdempotent

Book journal entry in the user's own Exact Online account from ChatGPT, Claude or any AI agent. Returns how to do it in Exact Online step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Exact Online Cloud Browser. Exact Online's official API: Yes.

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

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?

Beyond the annotations, the description explains that the tool opens nothing by itself, returns screen/button/field-level instructions, and relies on browser tools for execution. This is valuable behavioral context for a read-only guide tool, though it does not discuss authentication, rate limits, or error behavior.

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 description is reasonably short and front-loads the workflow, but it contains some low-value phrasing such as 'from ChatGPT, Claude or any AI agent' and the cryptic 'Exact Online's official API: Yes.' It could be tighter and clearer without losing meaning.

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?

Given that there are no parameters and no output schema, the description is complete enough: it says what the return is (step-by-step screens, buttons, fields) and that execution happens through browser tools. It leaves some ambiguity around the 'official API' sentence and does not specify any input prerequisites, but the core call context is 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?

The tool has zero parameters and the schema is empty, so there is no parameter meaning for the description to add. The baseline for a parameterless tool is 4, and nothing in the description misrepresents inputs.

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 states a specific resource (journal entry in Exact Online) and clarifies that the tool returns step-by-step instructions rather than performing the booking. It is distinguishable from browser-action siblings by explicitly handing off execution to cotlet_browser_* tools, though the opening phrase 'Book journal entry' initially sounds like a mutation and requires the second sentence to disambiguate.

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 clearly indicates the workflow: first get the step-by-step guidance, then perform the booking with cotlet_browser_* tools in the user's Exact Online Cloud Browser. It gives useful context and a next step, but does not explicitly state when not to use this tool or name any alternative API-based booking route.

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

All Exact Online 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?