Skip to main content
Glama
Sign In
Cuéntica MCP

Cuéntica MCP

by dacmail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_transfer

Destructive

Update a bank transfer with new details: amount, concept, accounts, date, and payment method. Requires user confirmation before applying changes.

Instructions

⚠️ Actualiza un traspaso. Confirmar con usuario.

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": {
      "transfer_id": "<transfer_id>",
      "amount": "<amount>",
      "concept": "<concept>",
      "origin_account": "<origin_account>",
      "destination_account": "<destination_account>"
    },
    "name": "update_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_idYes
amountYes
conceptYes
origin_accountYes
destination_accountYes
dateNo
payment_methodNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

The description adds the warning emoji and instruction to confirm with the user, which goes beyond the destructiveHint annotation by specifying a required user interaction. This provides additional behavioral context, alerting the agent to a necessary step before invocation.

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?

The description is extremely concise: two short sentences with a warning symbol. It is front-loaded with the key action and a critical usage note. Every word serves a purpose, and there is no 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?

Given the destructive annotation and presence of an output schema, the description adequately covers the need for user confirmation. It does not explain return values (unnecessary due to output schema), and the parameter details are left to the schema. For a destructive mutation tool, the description is sufficiently complete with the usage instruction.

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

Parameters1/5

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

The input schema has zero description coverage, and the description does not mention any parameter. With 7 parameters (5 required), the description provides no semantic guidance about what each parameter represents or how to use them, leaving the agent without field-level understanding.

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 explicitly states 'Actualiza un traspaso' (update a transfer), using a specific verb and resource. It clearly distinguishes itself from sibling tools like create_transfer, delete_transfer, get_transfer, and list_transfers by indicating an update operation.

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 description includes 'Confirmar con usuario' (confirm with user), providing a clear usage guideline about when to use this tool—only after user confirmation due to its destructive nature. It does not explicitly state when not to use or list alternatives, but the context is sufficient.

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