Skip to main content
Glama

Organizze

organizze_create_transfer

Cria uma transferência entre duas contas bancárias (suporta recorrência). Prefira NOMES de conta (não invente ids). Não envolve cartões de crédito.

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": {
      "amount": "<amount>",
      "date": "<date>",
      "credit_account": "<credit_account>",
      "debit_account": "<debit_account>"
    },
    "name": "organizze_create_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
doneNo
tagsNo
amountYes
recurringNo
descriptionNo
observationNo
periodicityNo
debit_accountYes
credit_accountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only signal non-readOnly, non-idempotent, and non-destructive, so the description carries the main behavioral burden. It adds useful behavior: recurrence is supported and account parameters should be names, not IDs. But it does not disclose side effects such as balance updates, validation behavior, or response/error details.

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 three short sentences with no filler. It front-loads the main purpose and then gives two high-value usage instructions, making it easily scannable for an AI agent.

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

Completeness3/5

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

For a 10-parameter mutation tool with no output schema, the description covers the core purpose and the account-naming convention but omits date formats, periodicity values, optional-field semantics, and any indication of the result. It is adequate for high-level selection but not fully complete for precise invocation.

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?

With 0% schema_description_coverage, the description must compensate. It clarifies the two account parameters by saying 'Prefira NOMES de conta' and hints at periodicity/recurrence semantics. However, it leaves amount, date, done, tags, observation, and periodicity values undocumented.

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 opens with a specific verb and resource: 'Cria uma transferência entre duas contas bancárias.' It also distinguishes itself from credit-card-related tools with 'Não envolve cartões de crédito' and adds recurrence scope, so an agent can clearly tell it apart from organizze_create_transaction and similar siblings.

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?

It gives clear context: use this for bank account transfers, and it explicitly excludes credit cards. It also provides a strong practical instruction to prefer account names rather than inventing IDs. However, it does not explicitly name alternative tools or describe when a regular transaction should be used instead of a transfer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.