Skip to main content
Glama

Outil.io

Get accounting settings

get_accounting_settings
Read-only

Lire les coordonnées et mentions de facturation du projet, avec leur version.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_accounting_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety and scope profile is covered. The description adds useful payload context that the annotations cannot provide: the tool returns billing contact details and legal mentions together with their version. It does not describe what happens when settings are unset, nor the response shape, which matters since there is no output schema.

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?

It is a single front-loaded sentence with no filler, which is well matched to a zero-argument getter. The only friction is that the description is written in French while the tool name, title, and annotations are in English, which is a stylistic mismatch rather than verbosity.

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 parameterless, non-destructive read, the description covers the essentials and notably indicates what is returned even though no output schema exists. It remains incomplete on the value of the 'version' field (is it for optimistic concurrency, or just informational?) and does not direct the agent to save_accounting_settings for writes.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing further the description could usefully clarify about arguments. No parameter semantics are needed or missing.

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 names a specific verb ('Lire') and a specific resource ('coordonnées et mentions de facturation du projet'), plus the notion that a version accompanies them. That is enough for an agent to distinguish this read tool from its write counterpart save_accounting_settings without opening the schema. It stops short of 5 because it never explicitly contrasts itself with the neighboring settings getters.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisite, and no reference to an alternative such as save_accounting_settings or get_workspace_settings. The read-only nature of the verb 'Lire' only implies the usage context, and the reader is left to infer that this is the counterpart to the save tool.

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.