Skip to main content
Glama

Outil.io

Get quote

get_quote
Read-only

Lire un devis : statut (draft, sent, viewed, accepted, refused, expired, cancelled), lignes, montants (centimes), liens publics, signature, commentaire du client, paiement (depositUrl / balanceUrl, paidAmount).

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 profile is covered. The description adds genuine value beyond that by disclosing the returned payload, including the important unit detail 'montants (centimes)' and the payment fields depositUrl/balanceUrl/paidAmount. It does not describe behavior on a missing or unauthorized id, so a 3 is appropriate.

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 with a dense parenthetical field list; every element (statuses, lines, amounts, links, signature, payment) carries information. No filler, though the field list is a flat enumeration rather than structured.

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?

For a low-complexity single-entity read with rich annotations and no output schema, the description adequately conveys what is returned, including enum-like status values and currency units. The remaining gap is the unexplained 'id' parameter and unspecified error behavior.

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

Parameters2/5

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

Schema coverage is 0% and the description never mentions the single required parameter 'id' — it does not say whether it is the quote identifier, nor anything about validity or scope. With only one obvious parameter the damage is limited, but the description fails to compensate for the coverage gap.

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 and resource ('Lire un devis') and then enumerates exactly what the read exposes (statut, lignes, montants, liens publics, signature, commentaire, paiement). An agent can distinguish this from the mutating quote siblings (create_quote, send_quote, delete_quote) without opening a schema, though it never names them explicitly.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as the quote-mutating tools. Usage is only inferred from the verb 'Lire' plus the required id.

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.