SnelStart MCP Server and API by Cotlet

Create sales invoice in SnelStart

snelstart_create_sales_invoice

Read-onlyIdempotent

Create sales invoice in the user's own SnelStart account from ChatGPT, Claude or any AI agent. Returns how to do it in SnelStart step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's SnelStart Cloud Browser. SnelStart's official API: Yes, but it is gated (checked 14 Oct 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": "snelstart_create_sales_invoice"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Consistent with readOnlyHint=true and destructiveHint=false: the description says it 'opens nothing by itself', confirming no side effects. It adds context the annotations cannot convey — what the output contains (screens, buttons, fields) and that SnelStart's official API is gated, which explains why browser automation is the path.

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

Conciseness4/5

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

The operative content (guidance-only behavior, follow-up with browser tools, API status) is front-loaded and earns its place. The phrase 'from ChatGPT, Claude or any AI agent' is marketing filler that adds nothing for an agent, a minor deduction.

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 input schema, no output schema, and only a read-only annotation, the description carries the full load and mostly does: it explains what is returned (step-by-step screens, buttons, fields) and what to do next. It does not specify the format or shape of the returned procedure, but that is a small gap for such a simple tool.

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 description correctly describes no inputs, so there is no semantic gap to fill. Baseline 4 applies for a no-parameter 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 concrete verb and resource (create sales invoice in SnelStart) and immediately clarifies that the tool itself returns step-by-step guidance rather than performing the write. The 'opens nothing by itself; then do it with the cotlet_browser_* tools' sentence cleanly distinguishes it from the browser automation siblings.

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?

Clearly signals the workflow: call this first to get the SnelStart procedure, then execute it via the cotlet_browser_* tools in the SnelStart Cloud Browser. It does not give explicit exclusions (e.g., when to skip it and use the official API instead), so it stops short of full routing guidance.

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

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