Skip to main content
Glama

Quote a document

quote_document
Read-only

Free price check: screens the file (format, pages, words, scanned pages) and returns the price, or why it can't be processed. Nothing is stored and nothing is charged.

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": {
      "files": "<files>"
    },
    "name": "quote_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesOne PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart upload).
localeNoLanguage of the error message and notes (English if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total."New value: +"One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart upload)."
    • addedInput schema / properties / locale
      Added value: +{
      +  "description": "Language of the error message and notes (English if omitted)",
      +  "enum": [
      +    "ja",
      +    "en"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description declares that nothing is stored and nothing is charged, and that failure yields an explanatory reason rather than an error. It does not mention rate limits or the shape of the pricing response, so it is informative but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero redundancy, with the free/no-storage/no-charge guarantees front-loaded where the agent will read them first.

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?

There is no output schema, but the description tells the agent what comes back (a price, or the reason processing is impossible), which is the essential return contract for a quote tool. A brief note on what the price response includes would make it fully complete.

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 files (count, formats, size limits, base64 overhead) and the locale enum are already fully documented in structured fields. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a concrete verb (screens/checks price) and resource (the file/document), plus the exact checks performed (format, pages, words, scanned pages). It is immediately distinguishable from siblings like create_order because it explicitly charges nothing and returns a price or a rejection reason.

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?

'Free price check... Nothing is stored and nothing is charged' implies this is the pre-flight step before creating an order, but create_order is never named and no explicit when-to-use/when-not-to-use routing is given. The agent must infer the quote-then-order workflow from the surrounding toolset.

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