arborists

search_listings

Read-onlyIdempotent

Search published tree care companies by text, place and category.

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

Input Schema

Name	Required	Description
`q`	No	Search text, with at least one letter or digit. Matches name, categories, attributes, description and place. Typos fall back to close matches.
`city`	No	City slug, from /places.
`sort`	No	`relevance` needs `q` and is the default with it. `name` is the default without `q`. `recent` is newest first.
`limit`	No	Items per page.
`cursor`	No	`page.nextCursor` from the previous response. Opaque. Send the same filters and `limit`.
`region`	No	Region slug, from /places.
`country`	No	ISO 3166-1 alpha-2 country code, any case. A country the directory does not cover, as listed in /places, gives 400.
`category`	No	Category slug, from /categories. A parent slug also matches its children.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already disclose that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful context that only published companies are searched. It does not add further behavioral detail about pagination, result ordering, or error conditions.

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?

The description is a single front-loaded sentence with no wasted words. It states the action and resource immediately.

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?

For an eight-parameter search tool, the description is adequate but thin. The schema fully covers parameters and annotations cover safety behavior, but the description does not mention pagination, sorting, or what a result set contains.

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 the input schema already documents all eight parameters thoroughly. The description maps its broad notions of text, place, and category to the available filters, but adds no syntax or constraint detail beyond the schema.

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 gives a clear verb and resource: searching published tree care companies. It also names the primary search dimensions (text, place, category). It does not explicitly differentiate itself from sibling tools such as get_listing or list_places.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool is used to search companies, but it gives no explicit guidance on when to use it instead of get_listing, list_places, or list_categories. It also provides no exclusions or prerequisites.

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

All arborists tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?