Chicago Demolition Leads | Salvage Signal

Search Chicago salvage signals

search_salvage_signals

Read-onlyIdempotent

Use when a human or agent needs specific current Chicago demolition-permit prospects, especially by material, urgency, or result count. For an aggregate trend summary and fixed watch list, use get_chicago_reuse_brief instead. Results are public prospecting clues, never site-access permission or inventory guarantees.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of ranked signals to return.
`urgency`	No	Salvage Signal urgency band.	all
`material`	No	Material or building-characteristic filter.	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
`market`	Yes
`safety`	Yes
`source`	Yes
`signals`	Yes
`dataMode`	Yes
`signalCount`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, open world, and non-destructive. The description adds that results are 'public prospecting clues' and not permissions or inventory guarantees, providing further context. No contradictions. Could mention rate limits or freshness but not necessary.

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 sentences, front-loaded with purpose and usage, every sentence adds value. No fluff or repetition.

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?

The description covers purpose, usage guidelines, limitations, and alternatives. Combined with a full output schema and annotation hints, the tool is complete and well-documented for an agent to use correctly.

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 describes all 3 parameters fully with types, defaults, and enums (100% coverage). The description does not add further parameter-specific details, so a baseline score of 3 is appropriate.

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?

The description clearly states the verb (search), resource (salvage signals), and distinguishes the tool from its sibling get_chicago_reuse_brief by specifying it is for specific prospects rather than aggregate summaries.

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

Usage Guidelines5/5

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

Explicitly states when to use (specific current prospects by material, urgency, count) and when not to use (for aggregate summary, use get_chicago_reuse_brief). Also notes caveats like results are public clues and not permissions or guarantees.

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

All Chicago Demolition Leads | Salvage Signal tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with explicit cross-references in descriptions to prevent confusion. get_chicago_reuse_brief vs search_salvage_signals are differentiated by aggregate vs. specific, and get_salvage_signal_offer vs get_subscription_handoff are separated by factual info vs. checkout flow.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case (get_*, search_*), with no mixing of conventions or ambiguous verbs. The naming clearly indicates action and target.

Tool Count5/5

With 4 tools, the set is tightly scoped to the domain of Chicago demolition leads and Salvage Signal subscriptions. Each tool serves a necessary function without redundancy or excess.

Completeness5/5

The tool surface covers the core user journeys: aggregate overview, specific search, service information, and subscription handoff. No obvious gaps are present for the stated purpose of providing leads and signup information.

Resources

Need Help?