Skip to main content
Glama

StartDrugRehab.com Treatment Directory

List states or cities

list_locations
Read-only

Without arguments, lists states covered with facility counts. With a state, lists its cities with counts and directory URLs.

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

Input Schema

NameRequiredDescriptionDefault
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing what comes back in each mode (facility counts, directory URLs) and that the tool behaves as a hierarchy drill-down. It says nothing about pagination, ordering, or what happens if the state string is unrecognized.

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

Conciseness5/5

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

Two short sentences, each covering one mode, with the no-argument case front-loaded. No filler, no restatement of the name or title.

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 usefully summarizes the returned data (counts, directory URLs) in both modes, and with only one optional parameter the surface area is small. The main remaining gap is the accepted format of the state value, which an agent must guess before calling.

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 0% for the single 'state' parameter, so the description must carry the meaning, and it does explain the parameter's effect on output (switches from state list to that state's cities). It does not specify the expected format, e.g. full name versus two-letter code, or whether matching is exact or fuzzy.

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?

The description names a specific verb (lists) and resource (states or cities), and spells out the two operating modes: bare call returns states with facility counts, call with a state returns that state's cities with counts and directory URLs. It doesn't reference the sibling tools (get_treatment_center, search_treatment_centers) to sharpen the boundary, but the tool's own function is unambiguous.

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?

Usage is stated conditionally and concretely: omit the argument for the state-level rollup, supply a state for the city-level listing. That is clear when-to-use guidance for both modes. It stops short of exclusions or pointing to search_treatment_centers when the agent actually wants facility records rather than geography.

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