SnelStart MCP Server and API by Cotlet

Upload document in SnelStart

snelstart_upload_document

Read-onlyIdempotent

Upload document 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_upload_document"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description's "opens nothing by itself" is consistent and reinforces that no side effect occurs. It adds genuinely useful behavioral context beyond the annotations: the return is a step-by-step procedural guide (screens, buttons, fields) and the official API is gated. Return format detail is modest but adequate for a no-parameter guide tool.

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 key constraint (returns instructions, performs nothing) is front-loaded and stated in the first sentence. The closing API-status note is somewhat tangential and the parenthetical about the check date feels like noise, but the description remains compact and readable.

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, non-destructive guide tool with no output schema, the description covers what it returns (step-by-step SnelStart screens/buttons/fields), that it has no side effects, and how to continue the task with browser tools. That is sufficient for an agent to select and use it 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, so the schema carries no semantics to supplement and the description is not expected to explain inputs. Baseline 4 applies; no parameter-related gaps exist.

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 pairs a specific verb and resource ("Upload document in the user's own SnelStart account") and immediately clarifies it returns step-by-step SnelStart instructions rather than performing the upload. The only weakness is that the name/verb 'upload' is at odds with what the tool actually does, which could momentarily mislead until the second clause is read.

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 workflow explicitly: get the step-by-step guide here, then perform the action with the cotlet_browser_* tools in the user's SnelStart Cloud Browser. It also notes the official API is gated, steering the agent away from an API path. No explicit 'when not to use' clause, which keeps it from a 5.

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?