Skip to main content
Glama
Sign In

Invoice Simple MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create estimate in Invoice Simple

invoice_simple_create_estimate
Read-onlyIdempotent

Create estimate in the user's own Invoice Simple account from ChatGPT, Claude or any AI agent. Returns how to do it in Invoice Simple step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Invoice Simple Cloud Browser. Invoice Simple's official API: Invoice Simple publishes no public API, API keys or developer documentation; its plans offer built-in payment integrations instead (checked 8 Nov 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": "invoice_simple_create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower; the description still adds real context by saying it 'opens nothing by itself' and that the return value is sequential screen/button/field guidance. The note that Invoice Simple has no public API, keys, or developer docs (checked 8 Nov 2026) explains why a browser flow is required. That date is in the future relative to typical training data, which slightly undercuts the claim's credibility.

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 core behavior and hand-off are front-loaded in the first sentence. The API-availability sentence is useful justification but runs long, and the 'checked 8 Nov 2026' timestamp is noise that may confuse an agent.

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, read-only guidance tool with no output schema, the description covers what it returns, that it has no side effects, and what to do next. Nothing essential to correct invocation is missing.

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 baseline of 4 applies. The description correctly implies no input is needed beyond the user's intent.

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 the resource (an estimate in the user's Invoice Simple account) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than creating anything. That resolves the ambiguity in the name 'invoice_simple_create_estimate'. It does not name its sibling invoice_simple_create_invoice, so the differentiation is only implied.

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 gives clear routing: get the steps here, then execute with cotlet_browser_* tools in the Cloud Browser. That is a concrete alternative and hand-off path. It stops short of stating when NOT to use it (e.g., when an API path or an existing estimate exists).

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

All Invoice Simple MCP Server and API by Cotlet toolsInspect
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