Skip to main content
Glama

List quotations

list_quotations
Read-onlyIdempotent

Quotations by status — e.g. the ones sent to a customer and not confirmed yet — with net and gross amounts and totals. PMs and admins only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50
statusNoawaiting_confirmation = published, not confirmed by the customer yet. Default awaiting_confirmation
customer_idNoFrom search_customers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "awaiting_confirmation",
      -  "draft",
      -  "approved",
      -  "confirmed",
      -  "canceled",
      -  "all"
      -]New value: +[
      +  "awaiting_confirmation",
      +  "draft",
      +  "confirmed",
      +  "canceled",
      +  "all"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuine behavioral fact not in the annotations: the tool is restricted to PMs and admins, which affects whether an agent should attempt the call. It omits pagination/truncation behavior for results.

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 filter, payload, and audience with no filler. The clipped fragment style ('e.g. the ones sent to a customer...') reads slightly informal but stays information-dense rather than padded.

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 read-only, three-optional-parameter list tool with full schema coverage and no output schema, this is nearly sufficient: it names the returned monetary fields and the permission gate. The remaining gap is that nothing states result volume or pagination behavior when limit is hit.

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 100%, so the schema already explains limit, status enum values, and customer_id sourcing from search_customers. The description's only parameter-adjacent contribution is the status example, which the schema states explicitly; baseline 3 is appropriate.

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 the resource (quotations), the primary filter axis (status), and the payload returned (net/gross amounts and totals), which is more than the name alone conveys. It doesn't name a distinguishing boundary against list_invoices, but 'quotations' is a distinct enough resource that an agent can identify the tool's domain.

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?

The clause 'the ones sent to a customer and not confirmed yet' implicitly demonstrates the awaiting_confirmation use case, and 'PMs and admins only' sets an access precondition. There is no explicit when-to-use versus list_invoices or guidance on choosing 'all' vs a specific status, so routing 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