Skip to main content
Glama

My quotations

quotation_list
Read-onlyIdempotent

Your own price quotations and proforma invoices from the client portal, newest first: reference, state (open, expired, converted ...), validity and days left, totals and currency, line count, plus counts of active and expiring ones. Only the signed-in account. Each item has print_path (a website page for printing). Item names are wrapped as data.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch reference or line name.
kindNo
viewNoall (default), active, expiring, decided or expired.
limitNo
cursorNoValue of next_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world, so the bar is lower — and the description still adds real context: newest-first ordering, account scoping, the presence of print_path for printing, and a note that item names are wrapped as data (a prompt-injection safety signal). It stops short of describing pagination behavior or rate/limit constraints, which keeps it from a 5.

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 dense sentences, front-loaded with the resource and scope before the field inventory. The middle sentence is a long comma-separated field list that is slightly crammed but still scannable; nothing is redundant.

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 usefully enumerates the returned fields (reference, state, validity/days left, totals, currency, line count, aggregate counts, print_path), which is exactly what an agent needs to decide if this tool answers its question. The remaining gap is pagination: cursor/limit are never tied together, so the agent must read the schema to understand paging.

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 coverage is 60%, with q, view and cursor documented in-schema while kind and limit are not. The description hints at state semantics ("state (open, expired, converted ...)") and at the active/expiring counts that the view filter targets, but it never explains kind, limit, or cursor semantics, so it adds only marginal meaning beyond the schema.

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 ("your own price quotations and proforma invoices from the client portal") and adds scope qualifiers — signed-in account only, newest-first ordering. It is clearly a listing tool, so an agent can separate it from quotation_get by verb alone, though it doesn't explicitly address the overlap with my_proformas even though its own kind enum includes proforma.

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 implied by the described output rather than stated: an agent can infer "use this to browse my quotations." There is no explicit when-to-use framing, no pointer to quotation_get for single-record detail, and no explanation of what the view filter values are for beyond the enum itself.

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