Skip to main content
Glama

Search Locations Tool

search-locations
Read-only

Lists physical locations in the authenticated workspace. Use to search locations in the connected business. Returns count, locations, scope.

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": "search-locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of location records to return; defaults to 20.
queryNoLocation name to search for.
statusNoactive, archived, or all.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
locationsYesBounded locations records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of location records to return; defaults to 20."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "locations": {
      +      "description": "Bounded locations records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "locations",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description's added behavioral note, "Returns count, locations, scope," duplicates what the output schema already provides and says nothing about pagination behavior or how the status filter affects results.

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 short sentences, front-loaded with the core purpose and free of filler. The middle sentence about searching in the connected business is close to redundant with the opening statement, a minor inefficiency.

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?

With annotations covering the safety profile, a 100%-covered input schema, and an output schema documenting the return shape, the description only needs to state purpose and scope, which it does. Nothing an agent needs in order to call this read-only search correctly is missing.

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 description coverage is 100%, so limit, query, and status are all documented in the input schema with defaults and constraints. The description adds no meaning beyond that, which is acceptable at full coverage but earns only the baseline.

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 opens with a specific verb and resource: "Lists physical locations in the authenticated workspace," which tells an agent exactly what the tool returns. It does not distinguish itself from the sibling get-location (single-record retrieval), leaving the list-vs-get distinction to be inferred.

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?

"Use to search locations in the connected business" implies a search/lookup context but adds no when-not guidance or explicit routing to get-location for a single known location. The usage cue is present but shallow and largely restates the first sentence.

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