Chicago Demolition Leads | Salvage Signal

Get Salvage Signal product and pricing facts

get_salvage_signal_offer

Read-onlyIdempotent

Use for factual questions about Salvage Signal's audience, free board, Daily Drop price, live aggregate founding availability, source, safety, or signup terms. This does not prepare a purchase link; use get_subscription_handoff only after a human expresses subscription interest.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`safety`	Yes
`source`	Yes
`dailyDrop`	Yes
`description`	Yes

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds behavioral context by stating it does not prepare a purchase link, which is consistent and adds value beyond annotations.

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 the purpose and scope. No wasted words; every sentence earns its place.

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 zero parameters and an output schema present, the description is complete. It covers what the tool does, its scope, and its limitations, which is sufficient for a simple read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100% trivially. Baseline for zero-parameter tools is 4, and no additional parameter info is needed.

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 ('use for factual questions') and the resource ('Salvage Signal's audience, free board, Daily Drop price, etc.'). It distinguishes itself from sibling tool get_subscription_handoff by specifying what it does not do.

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?

The description explicitly says when to use (for factual questions) and when not (not for purchase link, use get_subscription_handoff after human expresses interest). This provides clear guidance.

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?