Skip to main content
Glama

Outil.io

Save accounting settings

save_accounting_settings
Destructive

Configurer l’émetteur, les mentions TVA et les conditions de règlement. EUR. Administrateur requis. Aucun effet rétroactif sur les factures émises.

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": {
      "version": "<version>",
      "settings": "<settings>"
    },
    "name": "save_accounting_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
settingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Adds genuine context beyond the annotations: admin permission required, EUR-only scope, and the important clarification that changes have no retroactive effect on already-issued invoices, which meaningfully tempers the destructiveHint=true flag. It does not explain conflict/version behavior or what a failed save does, leaving a moderate gap.

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?

Four short fragments, purpose front-loaded, no filler. The telegraphic style ('EUR.' as a standalone fragment) is slightly cryptic but every element carries information; the description could have spent one of those fragments on 'version' instead.

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 destructive settings write with a 15+ field nested object, 0% schema coverage, and no output schema, the description covers the domain and permissions but leaves the required version parameter and conflict behavior undefined. An agent knows what the tool is for but not how to construct a safe call.

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 description coverage is 0% and the settings object is deeply nested, but the description does name the main field groups (issuer, VAT mentions, payment terms), which maps to most of the settings subtree. The required 'version' parameter and the iban field are never explained, so the concurrency token — the most semantically load-bearing parameter — remains opaque.

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?

States a specific verb ('Configurer') and enumerates the resources touched: issuer, VAT mentions, payment terms. The save-vs-get distinction from get_accounting_settings is implied by the verb, so an agent can route correctly, though the description never names the read counterpart for fetching current settings.

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?

Provides one real prerequisite ('Administrateur requis') but no explicit when-to-use guidance and no pointer to get_accounting_settings for retrieving the current version before overwriting. Usage is implied by the name and the field list rather than stated.

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.