Skip to main content
Glama

Little Works

draft_materials_order

Stage a multi-SKU materials purchase order (ship-to, lines, est. total). Completes in Discover Source / Message → Materials ops.

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": {
      "lines": "<lines>"
    },
    "name": "draft_materials_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNo
linesYes
notesNo
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
shipToNoJobsite / delivery label
contactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. 'Stage' and 'est. total' usefully imply a draft, non-final order, but there is no statement about permissions, whether staging commits anything, whether it is idempotent, or what happens after staging. For a commerce mutation with zero annotation coverage this leaves key behavior unexplained.

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

Conciseness3/5

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

The definition is short and front-loads the action, which is good, but the second sentence is cryptic internal shorthand that costs a line without conveying actionable meaning to an agent.

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

Completeness2/5

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

For a 7-parameter order-staging tool with no annotations, no output schema, and low schema coverage, the description is far too thin. It omits the outcome of staging, required auth context beyond the schema's apiKey note, and the meaning of most parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%, so the description must compensate. It mentions ship-to and lines (multi-SKU), which adds a little meaning, but five of seven parameters (job, notes, place, contact, quantity) get no explanation of purpose or format, and the relationship between lines and est. total is never clarified.

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?

The verb 'Stage' plus the resource 'multi-SKU materials purchase order' is specific, and the parenthetical (ship-to, lines, est. total) narrows what gets created. It does not explicitly distinguish itself from siblings like quote_materials_cart or buy_material, but the action itself is unambiguous.

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

Usage Guidelines2/5

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

'Completes in Discover Source / Message → Materials ops' hints at a flow stage but reads as internal jargon and gives no condition for choosing this over quote_materials_cart or buy_material. An agent cannot infer when staging is preferred to quoting or buying directly.

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