Skip to main content
Glama
Sign In
Cuéntica MCP

Cuéntica MCP

by dacmail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_invoice_public_link

Read-onlyIdempotent

Generate a public invoice link with an embedded Stripe payment button to share with clients for easy online payment.

Instructions

Link público de la factura para compartir con el cliente (incluye botón de pago Stripe).

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "get_invoice_public_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. Description adds useful context that the link includes a Stripe payment button, beyond what annotations provide. No contradictions.

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?

Single sentence that is front-loaded and concise. Every word adds value without redundancy.

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 simple retrieval tool with an output schema and clear parameter, description adequately covers functionality. Could mention that the link is public or that it requires a valid invoice, but overall sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the single required parameter 'invoice_id' is self-explanatory from its name and tool purpose. Description does not add further details on parameter formatting or constraints.

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?

Description clearly states the tool provides a public link for an invoice to share with the client, including a Stripe payment button. This distinguishes it from siblings like get_invoice (detail), get_invoice_pdf (PDF), and send_invoice_email (email).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for sharing a link with clients, but does not explicitly state when not to use or mention alternatives. No explicit guidance on choosing between this and related tools.

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