Skip to main content
Glama
Sign In
garu-mcp

garu-mcp

Official
by Garu-Pagamentos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pause_scheduled_charge

Temporarily halt a scheduled charge to stop reminders. Allowed when the charge is scheduled, due today, or overdue. Resume by calling the resume function.

Instructions

Pause a scheduled charge. No reminders fire while paused. Allowed from scheduled / due_today / overdue. Use resume_scheduled_charge to bring it back.

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": {
      "id": "<id>"
    },
    "name": "pause_scheduled_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesScheduled charge ID
reasonNoFree-form reason for the audit log

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description adequately discloses behavioral consequences (suppression of reminders, status constraints). Lacks details on permissions or idempotency, but covers core traits.

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?

Three concise sentences, front-loaded with the core action, each sentence adding valuable context 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 mutation without output schema, the description covers key aspects: action, effects, allowed states, and reversal. Could mention if it's idempotent or returns state.

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 100% so baseline is 3. Description adds no extra meaning for parameters beyond what the schema already provides.

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 the verb and resource ('Pause a scheduled charge') and distinguishes from siblings by mentioning 'resume_scheduled_charge' as the undo action.

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

Usage Guidelines5/5

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

Explicitly states when to use ('Allowed from scheduled / due_today / overdue'), what happens ('No reminders fire while paused'), and directs to the alternative tool for resuming.

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