Skip to main content
Glama

get_sales_draft

Read-onlyIdempotent

Read editable quote or invoice content and revision for a draft in the approved business.

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": {
      "id": "<id>"
    },
    "name": "get_sales_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description does add value beyond that by disclosing that the payload is 'editable' content plus a 'revision', and that the draft must belong to the approved business. It does not explain what the revision is for (e.g. optimistic concurrency when calling update_sales_draft) or what happens when the id is out of scope.

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 with no filler; the action and the returned content come first. The phrasing 'content and revision' is slightly compressed and ambiguous, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full annotation coverage and no output schema, the definition is close to sufficient. The remaining gaps are the meaning of 'revision' and the identity of the id, both of which an agent needs in order to use the returned data correctly alongside update_sales_draft.

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?

There is a single required parameter 'id' with 0% description coverage in the schema; the schema supplies only type, uuid format and a pattern. The description partially compensates by indicating the id refers to a draft in the approved business, but it never states whether the id is a draft id, document id or line-item id, nor what error surfaces for a wrong or out-of-scope id.

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 a concrete verb ('Read') and a concrete resource ('editable quote or invoice content and revision for a draft'), so an agent knows it returns draft document content rather than a list or a status. It is distinguishable from update_sales_draft and list_sales_documents by the read-plus-content framing, though it never names those siblings explicitly.

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 only implied: reading implies the counterpart update_sales_draft, and 'in the approved business' hints at tenant scoping. There is no explicit when-to-use statement, no exclusion (e.g. use list_sales_documents for non-draft documents), and no stated precondition such as draft type or state.

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