e-Boekhouden MCP Server and API by Cotlet

List open items in e-Boekhouden

e_boekhouden_list_open_items

Read-onlyIdempotent

List open items in the user's own e-Boekhouden account from ChatGPT, Claude or any AI agent. Returns how to do it in e-Boekhouden step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's e-Boekhouden Cloud Browser. e-Boekhouden'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": "e_boekhouden_list_open_items"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses the key behavioral fact that nothing is opened by itself and only instructions are returned, which is exactly what an agent needs to avoid assuming side effects. The trailing line 'E-Boekhouden's official API: Yes' is ambiguous and slightly at odds with the browser-based workflow described, which keeps this from a 5.

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 core message is front-loaded, but the sentences are long and run together, and the boilerplate 'from ChatGPT, Claude or any AI agent' plus the dangling 'official API: Yes' fragment do not earn their place. Trimming these would make the workflow instruction sharper.

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 parameters and no output schema, the description must say what comes back, and it does: step-by-step UI instructions plus a pointer to the browser tools that execute them. The only gap is the unexplained API-provenance line, which leaves a small ambiguity about whether an API path exists.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless tool is 4, but the description spends a clause on API provenance instead of confirming there is no input needed. Adequate but not additive.

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 names a specific resource (open items in e-Boekhouden) and clarifies the tool's real output: step-by-step instructions for the screens, buttons and fields to use. This corrects an ambiguity in the name ('List...' suggests it fetches data), so an agent can tell this is a guidance tool rather than a data-fetch tool.

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 states the follow-on action explicitly ('then do it with the cotlet_browser_* tools in the user's e-Boekhouden Cloud Browser'), which gives the agent a clear workflow. It does not name an exclusion or a directly competing tool, but the sequencing guidance is concrete.

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

All e-Boekhouden 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?