Skip to main content
Glama
Frihet-io

Frihet MCP Server

by Frihet-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Pause Recurring Invoice

pause_recurring_invoice
Idempotent

Pause an active recurring invoice template to stop new invoices from being generated. The template is preserved for later resumption.

Instructions

Pause an active recurring invoice template. No new invoices are generated while paused. The template is preserved — use resume_recurring_invoice to restart. / Pausa una plantilla de factura recurrente activa. No se generan nuevas facturas mientras esta pausada. Usa resume_recurring_invoice para reanudarla.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRecurring invoice template ID / ID de la plantilla de factura recurrente

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
dataNo
metaNo
messageNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.2
  2. Removedv1.15.2
  3. Changed3 schema fields changedv1.15.0
    • addedOutput schema / properties / data
      Added value: +{
+  "not": {}
+}
    • addedOutput schema / properties / meta
      Added value: +{
+  "not": {}
+}
    • removedOutput schema / required
      Removed value: -[
-  "success",
-  "id"
-]
  4. Addedv1.13.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate idempotent and non-destructive. Description adds that no new invoices are generated while paused and the template is preserved, aligning with annotations. 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?

Two sentences, front-loaded with the core action, then effect and reversion. No wasted words; bilingual version is fine.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description covers the purpose, effect, and how to undo. Complete for a state-change tool.

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?

Parameter 'id' is fully described in the schema (100% coverage). The description does not add extra meaning; baseline of 3 is appropriate.

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?

The description clearly states 'Pause an active recurring invoice template', with a specific verb and resource. It distinguishes from siblings like 'resume_recurring_invoice' by mentioning the resume action.

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?

Provides context for when to use (to stop generation temporarily) and explicitly mentions resume_recurring_invoice for restarting. Could be improved by noting when not to use, but sufficient guidance is given.

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