Skip to main content
Glama

Little Works

get_material

SKU detail (e.g. HARDIE-LAP-825), price, unit, certs, URLs.

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": "get_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU or slug, e.g. HARDIE-LAP-825

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the whole burden; it does at least disclose what comes back (price, unit, certs, URLs), which is meaningful because there is no output schema. It says nothing about read-only semantics, missing-SKU/error behavior, or data freshness, which is a gap for a tool with zero structured behavioral metadata.

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?

Extremely short and front-loaded with the key noun, with no wasted words. It is efficient, though clipping it to a fragment costs it a verb and a little clarity.

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 no output schema, listing the returned fields covers the most important unknown. Still, an agent gets no signal about when to call it versus list_materials or what happens on an unknown SKU.

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% and the single sku parameter is documented there, including the same HARDIE-LAP-825 example. The description repeats rather than extends that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "SKU detail" plus a list of returned attributes conveys that this fetches a single material by SKU, and the example SKU anchors the resource. However, it is a noun phrase with no verb, so the agent must infer that it is a read/fetch operation, and it does not explicitly distinguish itself from list_materials.

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 statement of when to use this instead of list_materials or any other sibling, and no prerequisites or exclusions. The singular 'SKU' implies one record versus a listing, but that is inference, not guidance.

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