Skip to main content
Glama

Little Works

list_materials_places

Fulfillment cities (Victoria, Oak Bay, Saanich, …).

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_materials_places"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing: no statement of whether this is a read-only lookup, whether results are static or depend on inventory or service areas, or whether authentication is required. For a zero-argument discovery tool the risk is low, but the description adds no behavioral context beyond the noun phrase.

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

Conciseness3/5

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

It is short with no filler, but it is a sentence fragment ending in an ellipsis rather than a front-loaded statement of what the tool returns. Brevity here is under-specification rather than disciplined conciseness.

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?

A simple zero-parameter tool needs only a clear statement of what it lists and how the result should be used, and that is missing. With no output schema and no annotations, an agent cannot tell whether the response is a plain array of city names or richer objects keyed to materials.

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; baseline 4 applies. The examples in the description are the only parameter-like signal and they are not needed for invocation.

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 is a noun fragment, 'Fulfillment cities (Victoria, Oak Bay, Saanich, …)', with no verb, so it never states the operation. It does clarify what 'places' means — cities where materials are fulfilled — and gives concrete examples, which keeps it above a pure restatement of the name, but the agent must infer that it returns a list.

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 guidance on when to call this versus the many sibling list_* tools (list_materials, discover_browse_places, list_booking_services). No prerequisites, no mention of whether it should be called to validate a city before buy_material or source_materials_for_job.

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