Skip to main content
Glama

WeGravel

List Materials

list_materials
Read-onlyIdempotent

List the materials WeGravel sells in bulk, delivered in Florida (soils, sands, gravel, mulch). Returns the slug, name, category, description, and unit of each material: the unit WeGravel sells it by ("yd3" = cubic yards, "ton" = tons). Call this first to get valid slugs for the other tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
materialsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety and idempotency are covered by structured data. The description adds useful domain context (bulk sales, Florida delivery area, unit vocabulary), but doesn't mention result size, ordering, or pagination. Since an output schema exists, the field list is somewhat redundant with that structured data.

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?

Three front-loaded sentences: scope, return shape, then call-order guidance. Efficient overall, though the enumerated return fields partly duplicate the output schema and cost some space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with full annotation coverage and an output schema, the description supplies everything an agent needs: what's listed, the delivery region, the unit semantics, and the fact that it should be called before dependent tools.

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?

Zero parameters, so the baseline is 4; nothing about parameter meaning is required. The description spends its words on return semantics instead, which is appropriate for a no-arg tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('List the materials WeGravel sells in bulk') with an explicit scope constraint (delivered in Florida) and the domain of returned records enumerated (soils, sands, gravel, mulch). It clearly distinguishes itself from siblings like get_prices or calculate_quantity, which operate on pricing and quantities rather than the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States an explicit call-order rule: 'Call this first to get valid slugs for the other tools,' which tells the agent this is a prerequisite discovery step. It doesn't name when NOT to use it, but for a zero-parameter catalog lister there's no plausible alternative to exclude.

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