Skip to main content
Glama
Sign In
cledara-mcp

cledara-mcp

by ilyesBen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get invoice download URL

get_invoice_url
Read-onlyIdempotent

Retrieve a temporary download URL for a transaction's invoice when hasInvoice is true; the link expires in 5 minutes.

Instructions

Get a download URL for the invoice attached to a transaction (only when hasInvoice is true). The URL expires after 5 minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transactionId": "<transactionId>"
    },
    "name": "get_invoice_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionIdYesTransaction ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior the annotations cannot express: the returned URL expires after 5 minutes. It does not say what happens if the precondition fails (error vs. null), which is the remaining gap.

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

Conciseness5/5

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

Two short sentences, zero filler, with the precondition placed before the expiry caveat. Every clause carries information an agent needs.

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 output schema, the description still tells the agent what is returned (a download URL) and its lifetime. For a one-parameter read tool this is nearly complete; only failure behavior when hasInvoice is false is unstated.

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?

Schema coverage is 100% and the single transactionId is documented as a UUID in the schema. The description adds meaning beyond that by tying the parameter to a transaction that must carry an invoice, clarifying which transactions yield a usable result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (download URL for an invoice attached to a transaction), plus the scope precondition hasInvoice=true. An agent can distinguish this from siblings like missing_invoices or list_transactions without opening the schema.

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?

The parenthetical '(only when hasInvoice is true)' gives a clear gating condition for invocation. It stops short of naming an alternative (e.g. missing_invoices) for the case where no invoice exists, so the when-not path is implied rather than routed.

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

Deploy Server

Other Tools