Skip to main content
Glama

List Industries

list_industries
Read-onlyIdempotent

List all supported industries grouped by family. Use this to find the right industry identifier for create_site.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare read-only, idempotent, closed-world and non-destructive, and the trailing paragraph largely restates those structured hints rather than adding new behavior. What the description does add beyond the annotations is the grouping structure of the result and the downstream dependency on create_site; it says nothing about output size, caching, or whether the list is stable across calls.

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?

The operative guidance is two tight, front-loaded sentences with no waste. The appended "Annotations: ... Why: ..." block duplicates what the structured annotations already convey, which is the only reason it is not a 5.

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 parameterless, non-destructive lookup with no output schema, the description supplies the essentials: what comes back (industries grouped by family) and why an agent would call it (to obtain a valid industry identifier for create_site). Nothing needed to invoke it correctly is missing.

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 no parameter semantics to explain; the empty schema is fully consistent with the description. Baseline 4 applies, with no gap for the description to compensate for.

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?

States a specific verb and resource ("List all supported industries") plus the shape of the result ("grouped by family"), which no sibling provides. An agent can immediately tell this is a zero-argument reference-data lookup, distinct from the create/list tools around it.

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?

Gives an explicit use case — "find the right industry identifier for create_site" — which ties the tool to the workflow that consumes its output. It does not state when-not to use it, but there is no sibling that overlaps, so the missing exclusion is immaterial.

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.