Skip to main content
Glama

Little Works

list_manufacturers

Manufacturers / brands on the specialty catalog — who supplies SKUs Little Works can order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_manufacturers"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeNoexterior|plumbing|hvac|electrical|tile|hardware

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It tells the agent the catalog scope but says nothing about read-only behavior, authentication, pagination, ordering, or what happens when the optional trade filter is omitted, leaving meaningful gaps for a list operation.

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

Conciseness5/5

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

A single, front-loaded sentence with no redundant wording. The scope and entity meaning are stated immediately, and every phrase contributes to identifying the resource.

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 simple list tool with one optional parameter, no output schema, and no annotations, the description covers what the resource is but not how results are shaped, paged, or filtered. It is minimally viable but leaves an agent to infer operational details.

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 description coverage is 100%, so the single optional 'trade' parameter and its enumerated values are already documented in the schema. The description adds no further meaning about filtering by trade or default behavior, so the baseline score is appropriate.

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 names the resource ('Manufacturers / brands') and its scope ('on the specialty catalog'), and clarifies what these entities represent ('who supplies SKUs Little Works can order'). This is a specific verb-and-resource statement, though it does not explicitly differentiate itself from siblings like list_materials or list_materials_places.

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: an agent can infer this is for browsing the specialty catalog's suppliers, but the description gives no explicit when-to-use guidance, no exclusions, and does not name an alternative for related lookups such as materials or places.

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