Skip to main content
Glama

Coordonnées de la société

get_company_settings
Read-onlyIdempotent

Paramètres métier de la société : nom, adresse, téléphone, TVA, devise, méthode de valorisation du stock, seuils. Les secrets (clés, licence) ne sont jamais renvoyés. (Lecture seule.)

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_company_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the trailing '(Lecture seule.)' adds nothing. What does add value is the disclosure that secrets (clés, licence) are never returned — a real behavioral constraint an agent could not learn from the annotations or 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?

A single front-loaded sentence covering contents plus one exclusion, with no filler. The parenthetical '(Lecture seule.)' is redundant against readOnlyHint=true and could be cut.

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?

With no input schema and no output schema, the description usefully enumerates the returned fields (including devise, stock valuation method, thresholds) and flags what is withheld. It could say slightly more about the shape of 'seuils' or units, but it is sufficient for a no-argument getter.

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?

Zero parameters, so per the baseline this is a 4. The description correctly gives no parameter guidance and instead spends its space on returned content.

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?

Names the resource precisely ('Paramètres métier de la société') and enumerates the fields returned (nom, adresse, téléphone, TVA, devise, méthode de valorisation du stock, seuils). No sibling covers company settings, so it is distinguishable from the get_*/list_* catalog without naming an alternative.

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 only implied: an agent can infer it should call this when it needs company identity/tax/currency data. There is no explicit when-to-use statement, no prerequisites, and no pointer to related tools for things like stock alerts that might seem adjacent.

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