Skip to main content
Glama

Little Works

search_materials

Search materials by query; optional city for jobsite delivery URLs.

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

Input Schema

NameRequiredDescriptionDefault
placeNoe.g. victoria-bc
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and discloses almost nothing behavioral: no result format, pagination, result limits, or permission requirements. The only behavioral hint is that the optional place affects jobsite delivery URLs, which is a useful but isolated detail.

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?

A single front-loaded clause with no filler; the required query is named first and the optional parameter second. The phrasing 'optional city for jobsite delivery URLs' is slightly compressed and ambiguous, which keeps it from a 5.

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?

The tool is simple (2 params, no nesting), but with no annotations and no output schema the description should say something about what a search returns or how results are scoped. It covers inputs adequately and outputs not at all.

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 coverage is 50% – query is undocumented in the schema – and the description does supply the role of both inputs, notably explaining that the 'place' parameter means a city tied to jobsite delivery URLs, which is real added meaning. It still leaves a naming mismatch ('city' vs 'place'), the expected query syntax, and whether multiple places are allowed unaddressed.

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 ('Search materials by query') and scopes the second parameter, so the agent can tell it apart from list_materials or get_material. It stops short of explicitly contrasting with those siblings.

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 implied by 'by query' – you call it when you have a search string – but there is no statement of when not to use it, no mention of list_materials or discover_search as alternatives, and no prerequisites.

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