Skip to main content
Glama

Outil.io

List quotes

list_quotes
Read-only

Lister les devis avec statut, montants et liens. Filtres : status, contactId, dealId, prospectId, q.

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": "list_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
pageNo
limitNo
dealIdNo
statusNo
contactIdNo
prospectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "draft",
      -  "sent",
      -  "viewed",
      -  "accepted",
      -  "refused",
      -  "expired"
      -]New value: +[
      +  "draft",
      +  "sent",
      +  "viewed",
      +  "accepted",
      +  "refused",
      +  "expired",
      +  "cancelled"
      +]
  2. Added

TDQS

B3.2/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 usefully discloses the shape of returned data (status, amounts, links) since there is no output schema, but says nothing about pagination, ordering, or default result size.

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?

Two short clauses with the purpose front-loaded and filters second; no filler. Slightly terse for the amount of undocumented behavior, but structurally clean.

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?

No annotation contradiction exists.

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%, so the description carries the burden and does name five of the seven parameters (status, contactId, dealId, prospectId, q). However page and limit are entirely unmentioned, leaving paging and default page size undocumented in both schema and description.

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 a specific verb and resource ('Lister les devis') and even states the fields returned (statut, montants, liens), which distinguishes it from sibling list tools that target other resources. It does not explicitly contrast with any sibling, so it stops short of 5.

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?

The filter list implies the tool can be narrowed by status/contact/deal/prospect/keyword, but there is no statement of when to use this versus another listing tool, no prerequisites, and no mention of behavior with no filters applied (full list?).

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.