Skip to main content
Glama

One quotation

quotation_get
Read-onlyIdempotent

One of your own quotations or proformas by reference (BRM-PF-...): lines with prices, charges, delivery and payment terms, your note, versions and timeline. Someone else's reference returns not found. No PDF and no accept over MCP; use print_path on the website. Free text is wrapped as data.

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": {
      "ref": "<ref>"
    },
    "name": "quotation_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesQuotation reference.
includeNoSections to include. Default all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses ownership scoping and the resulting not-found behavior for foreign references, the full returned payload, and the deliberate capability boundary that PDF/accept are unavailable over MCP. 'Free text is wrapped as data' also flags injection-handling behavior, which is exactly the kind of context annotations cannot convey.

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?

Front-loaded with the resource and identifier format, followed by two short sentences covering the foreign-reference case and the capability limits. Dense but every clause carries information; phrasing like 'no accept over MCP' is terse enough to be slightly cryptic.

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 takes on the burden of describing the return payload, which it does thoroughly, and it covers the main failure mode. Missing are any hints on version/timeline ordering or pagination semantics, but nothing essential to a correct call is absent.

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 100%, so the ref pattern and the include enum are already documented in structured fields, putting this at the baseline. The description adds a little by naming the content categories (lines, terms, timeline) that the include values select, but it never maps them to the 'include' parameter explicitly.

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?

The description states a specific retrieval verb and resource: 'One of your own quotations or proformas by reference (BRM-PF-...)', then enumerates exactly what comes back (lines with prices, charges, delivery/payment terms, note, versions, timeline). The phrase 'One of your own' plus the singular reference cleanly separates it from a list-style sibling such as quotation_list without needing to name it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear when-not condition ('Someone else's reference returns not found') and routes capability-seeking callers elsewhere ('No PDF and no accept over MCP; use print_path on the website'). What it lacks is an explicit pointer to the list tool for callers who don't yet have a reference, but the context is otherwise unambiguous.

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