Skip to main content
Glama

Little Works

connect_manufacturer

Onboard a manufacturer: create visible request + Digital Storefront asset they will own (existing cycle). Then they list SKUs and route POs.

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

Input Schema

NameRequiredDescriptionDefault
nameYesManufacturer / shop name
notesNo
placeNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
tradesNo
sampleSkusNo
contactEmailNo
contactPhoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Manufacturer / brand name"New value: +"Manufacturer / shop name"
    • addedInput schema / properties / place
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior beyond the name: a visible request is created and ownership of an asset is transferred, which is more than a bare 'connect'. However, it omits required authorization beyond the apiKey parameter, whether the operation is idempotent or reversible, what happens to pre-existing entities, and what the call returns.

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?

Two compact sentences, front-loaded with the action and its effects. The only waste is the opaque parenthetical '(existing cycle)', which adds ambiguity rather than information.

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?

This is a complex mutation tool with eight parameters, no annotations, and no output schema, yet the description leaves the authorization model, return values (e.g., created IDs or confirmation link), parameter meanings, and failure modes unstated. For a multi-entity onboarding operation the definition is underspecified.

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 coverage is only 25% (name and apiKey), so the description needs to compensate and does not. It never mentions trades, sampleSkus, place, notes, contactEmail, or contactPhone; 'they list SKUs' obliquely hints at the SKU parameters but gives no format or expectation for them.

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 ('Onboard a manufacturer') and enumerates the concrete side effects: creating a visible request plus a Digital Storefront asset the manufacturer will own. This is distinct from the sibling get_manufacturer, though jargon like 'Digital Storefront asset' and '(existing cycle)' is not defined, so the purpose is clear in outline but not in detail.

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 when-to-use guidance, no preconditions, and no explicit alternative named. The trailing sentence ('Then they list SKUs and route POs') describes what happens after onboarding rather than when an agent should choose this tool over other creation tools such as buy_material or draft_materials_order.

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