Skip to main content
Glama

Place categories

bl_categories
Read-onlyIdempotent

List Balad place categories and their slugs to find the exact category slug for nearby, nearest-by-drive, or along-route place searches.

Instructions

List Balad's place categories with the slug bl_nearby takes, grouped (food, health, shopping, services...).

Use it for the exact slug for bl_nearby, bl_nearest_by_drive or bl_along_route.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond that by characterizing the output as grouped category entries containing slugs that serve as valid input values for downstream tools, which tells the agent this is a dependency/discovery call rather than a search.

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?

Two short sentences with no filler, and the core purpose is front-loaded before the routing sentence. The phrase 'with the slug bl_nearby takes' is slightly compressed and reads awkwardly, but it costs no extra length.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining returns and does so by describing grouped categories with slugs plus examples. For a zero-parameter lookup that is close to complete; only the exact response shape (flat list vs grouped object) remains unstated, which is a minor gap.

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 the baseline is 4 and there is no schema semantics left to explain. The description wisely spends its words on the output contract instead of inventing parameter guidance.

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 (List) and resource (Balad's place categories) and immediately names the payload an agent cares about: the slug consumed by other tools. The parenthetical examples (food, health, shopping, services) make the return content concrete and distinguish this from all eight siblings.

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?

Explicitly routes usage: call this to obtain the exact slug required by bl_nearby, bl_nearest_by_drive or bl_along_route. That is a clear when-to-use clause tied to named alternatives. It stops short of stating the inverse (e.g. do not call this for free-text queries, use bl_search), so it is strong but not fully exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.