Skip to main content
Glama

Ajouter une transaction

dandori_add_transaction

Ajouter une transaction budget (revenu ou dépense). Sans Plus, le nombre est limité (le refus le dit).

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": {
      "type": "<type>",
      "amount": "<amount>",
      "date": "<date>"
    },
    "name": "dandori_add_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate (YYYY-MM-DD)
typeYesType : income (revenu) ou expense (dépense)
amountYesMontant POSITIF (le type décide du sens)
space_idNoID de l'espace (champ spaces de dandori_daily_summary) ; par défaut l'espace principal
descriptionNoLibellé / description
budget_category_idNoID de la catégorie budget, du même espace (voir dandori_budget_dashboard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnly=false, destructive=false, idempotent=false), and the description adds one genuinely non-obvious trait: non-Plus accounts are capped and the refusal message communicates it. It says nothing about validation failures, duplicates (non-idempotent), or what the call returns, so the added context is real but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action front-loaded and no filler. The phrase 'Sans Plus' is slightly cryptic (subscription tier) and would benefit from one clarifying word, but the text is efficiently sized.

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?

With a fully documented six-parameter schema and no output schema, the description covers the core action and the quota caveat. It leaves open whether the created transaction is returned and how duplicate submissions behave, which matters for a non-idempotent write 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?

Schema coverage is 100%, so all six parameters are already documented, including the income/expense enum, the positive-amount rule, and the space_id default. The description's '(revenu ou dépense)' merely restates the enum and adds no format or constraint detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Ajouter une transaction budget') and disambiguates the domain with '(revenu ou dépense)'. It does not explicitly contrast with siblings such as dandori_budget_dashboard, but the action is unmistakable.

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?

Usage is implied by the verb — call this to record a new income or expense entry — but there is no explicit when-to-use/when-not guidance or pointer to a sibling for reading budget data. The only conditional note concerns the Plus subscription quota.

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.

Resources