Skip to main content
Glama

Fiche prestation

get_service
Read-onlyIdempotent

Fiche d'une prestation par ID : prix HT, TVA, unité, facteurs de calcul (ordre des valeurs à donner dans calculations), minimum facturé, tarifs dégressifs, options, catégorie, description. (Lecture seule.)

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": {
      "id": "<id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la prestation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the trailing '(Lecture seule.)' is redundant repetition. Genuine added value comes from enumerating exactly which fields the returned record contains, including the note that the 'calculations' factors dictate the order of values to supply — this is behavioral context the annotations cannot provide.

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 that packs the resource, the access key (ID) and the returned fields without filler. The only wasted element is the parenthetical '(Lecture seule.)', which restates readOnlyHint already present in the annotations.

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 output schema, the description carries the burden of telling the agent what comes back, and it does so by listing the record's fields. It stops short of types or formats (e.g. whether prices are integer cents or decimals), which matters when the agent must interpret 'prix HT' and 'TVA'.

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?

Only one parameter, and the schema already documents it fully ('Identifiant de la prestation', required integer), so the 100% coverage baseline of 3 applies. The description adds 'par ID' and references 'calculations' ordering, but that reference pertains to the returned data, not to any input of this tool.

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?

States a specific verb+resource with scope: 'Fiche d'une prestation par ID', then enumerates the exact content of the record (prix HT, TVA, unité, minimum facturé, tarifs dégressifs, options, catégorie). An agent can immediately separate this single-record fetch from the list_* siblings in the catalog.

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?

'par ID' implies you must already hold an identifier, and '(Lecture seule.)' signals this is a lookup rather than a mutation. However no guidance is given on where to obtain the ID or which sibling to call when you only know a name or category, so usage is only implied.

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