Skip to main content
Glama

Little Works

materials_commerce_capabilities

Map of materials commerce tools — service is any transaction (quote → order → manufacturer fulfill).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries the full behavioral burden, yet it does not say whether the call is read-only, what the returned 'map' contains (tool names, descriptions, routing hints), or how it relates to the specific commerce tools. The lifecycle phrase adds domain framing but no operational context.

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?

It is a single front-loaded sentence with no redundant wording. Its brevity borders on under-specification rather than verbosity, which is preferable but leaves the reader with little to act on.

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 zero-parameter orientation tool with no output schema, the description should clarify what capability map is returned and how an agent should use it before calling specific commerce tools. It conveys the domain boundary but stops short of making the tool self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the 100% schema coverage and empty schema make this a baseline-4 case.

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 description names the domain ('materials commerce tools') and frames the service lifecycle as 'quote → order → manufacturer fulfill', which tells an agent the scope. However, 'Map of ...' is not a verb describing an action, and it does not distinguish this from sibling capability tools such as discover_capabilities or get_anything_capabilities.

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 call this versus the other discovery/capability siblings, nor any precondition or follow-up guidance. The lifecycle arrow implies it is an orienting entry point, but that is left for the agent to infer.

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