e-Boekhouden MCP Server and API by Cotlet

Add relation in e-Boekhouden

e_boekhouden_add_relation

Read-onlyIdempotent

Add relation 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_add_relation"
  }
}

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 mark it readOnly, idempotent, non-destructive, and closed-world, so the description does not need to restate safety. It adds the crucial behavioral clarification that it returns screens, buttons, and fields and opens nothing by itself, though the cryptic 'official API: Yes' fragment adds little and slightly muddies the picture.

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 clarification is present but buried in a run-on sentence, and phrases like 'from ChatGPT, Claude or any AI agent' and 'e-Boekhouden's official API: Yes' are promotional or cryptic filler. Front-loading the read-only/guidance nature would make it stronger.

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 guidance tool, the description explains what it returns (step-by-step screens, buttons, fields) and how to execute afterward via browser tools. It could be more explicit about scope or limitations, but is largely complete for the agent's decision.

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?

There are zero input parameters, so there is no parameter meaning for the description to carry and the baseline is 4. The description appropriately does not invent parameter details.

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 identifies the resource (a relation in the user's e-Boekhouden account) and clarifies in the second sentence that it returns step-by-step instructions rather than performing the addition. The opening imperative 'Add relation' still reads like an action, and no direct e-Boekhouden sibling is named for contrast, so it falls short of a 5.

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 explicitly says the tool opens nothing by itself and that the actual work should then be done with cotlet_browser_* tools in the user's e-Boekhouden Cloud Browser. That gives a clear use context and next step, though it does not specify the browser tool sequence or when to prefer this over direct API/bookkeeping alternatives.

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?