boilerpros

search_listings

Read-onlyIdempotent

Search published heating contractors 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.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds that only published listings are searched and nothing beyond that; it omits pagination behavior, result shape, and the typo fallback that only appears in the schema.

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?

A single tight sentence with no redundant phrasing. It is appropriately front-loaded, though the extreme brevity leaves gaps rather than wasting words.

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 8-parameter search tool with no output schema, the description is thin: it does not explain result content, pagination flow, or empty-result behavior, relying on the schema for all parameter detail. Annotations cover the safety side, so this is adequate but not complete.

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%, including sort defaults, cursor reuse, and parent-category matching, so the schema carries parameter meaning. The description only maps the high-level facets (text, place, category) and adds no syntax or format detail beyond that 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?

States a specific verb and resource ("Search published heating contractors") plus the facets searched (text, place, category). This distinguishes it from get_listing (single record) without explicitly naming alternatives, so it is clear but not sibling-differentiating.

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?

The word "published" implies only live listings are returned, which is useful implied context, but there is no explicit when-to-use/when-not guidance or routing to get_listing for a known ID. Usage must be inferred from the parameter set.

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

All boilerpros 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?