Skip to main content
Glama

Little Works

source_materials_for_job

Given a project/problem + place, return matched SKUs + buy/source/hire/book 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": {
      "job": "<job>"
    },
    "name": "source_materials_for_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYese.g. vinyl siding Victoria
placeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return shape at a high level (matched SKUs and URLs), but says nothing about side effects, permissions, rate limits, matching quality, or whether the tool merely returns URLs versus initiating any purchase/hire/book action.

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?

The definition is a single front-loaded sentence with no filler. It is appropriately brief, though the compressed phrasing leaves some ambiguity that a slightly more structured sentence could resolve.

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?

With no annotations and no output schema, the description should do more to explain behavior and return values. It names the output categories but omits usage guidance, prerequisites, and safety context that an agent would need before invoking it confidently.

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 50%, with the 'job' parameter already having an example. The description adds some meaning by reframing 'job' as a project/problem and pairing it with 'place', but it does not clarify the expected format or scope of 'place' beyond that.

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 description states a specific action: given a project/problem and place, return matched SKUs plus buy/source/hire/book URLs. That is clear enough to distinguish it from generic listing or search tools, but it does not explicitly name or contrast with siblings like search_materials or 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?

The only usage context is the implied 'given a project/problem + place' framing. There is no explicit guidance on when to use this tool versus alternatives such as search_materials, list_materials, or buy_material, nor any exclusions or prerequisites.

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