Skip to main content
Glama

Little Works

buy_material

Start a materials buy for one SKU (+ qty) to a jobsite city — quote + checkout / Discover Source path.

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": {
      "sku": "<sku>"
    },
    "name": "buy_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYes
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / quantity
      Added value: +{
      +  "type": "number"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for what is evidently a commerce/mutation operation. It does not say whether this actually places an order or only produces a quote, whether checkout is automatic, what it costs, whether it is idempotent, or what permissions/credentials beyond the schema's apiKey note are needed. 'Quote + checkout' actively leaves the agent unsure whether money is spent.

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?

It is a single front-loaded sentence with no filler, which is good. But the terse fragments ('+ qty', 'Discover Source path') trade clarity for brevity, so compression has gone past the point of usefulness.

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 4-parameter commerce tool with no annotations and no output schema, the definition is thin. An agent cannot determine from the description whether the call commits a purchase, what the response contains (quote vs order confirmation), or how failures/auth behave, which are exactly the gaps the description exists to fill.

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 only 25% (only apiKey is documented), so the description must compensate. It does clarify three of four parameters by mapping them: sku = the single SKU, quantity = qty, place = jobsite city, which is genuinely useful since 'place' is otherwise opaque. However, it adds no constraints on quantity units/defaults, place format, or what apiKey unlocks beyond the schema's own note.

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 specific verb and resource: 'Start a materials buy for one SKU (+ qty) to a jobsite city'. The single-SKU scope implicitly separates it from siblings like buy_project and buy_recipe, though it never names them. The trailing 'quote + checkout / Discover Source path' muddies rather than sharpens the purpose.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the phrase 'one SKU' that this is the narrow single-item path versus buy_project/buy_recipe, and 'Discover Source path' is unexplained jargon that gives no actionable routing signal.

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