Skip to main content
Glama

Chicago Demolition Leads | Salvage Signal

Get the Chicago Teardown-to-Reuse Brief

get_chicago_reuse_brief
Read-onlyIdempotent

Use for a current Chicago teardown-to-reuse overview, aggregate trends, and a ranked watch list with source and safety context. For a material- or urgency-filtered candidate list, use search_salvage_signals instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
marketYes
safetyYes
sourceYes
summaryYes
dataModeYes
watchListYes

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint; description adds specific output context (aggregate trends, ranked watch list, source and safety context) without contradiction.

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 alternative, no wasted words.

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?

Tool has no parameters, good annotations, and description clearly states purpose and when to use alternatives; fully adequate for an agent.

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, so parameter semantics are trivial; description provides sufficient context beyond schema.

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?

Description explicitly states the tool provides a Chicago teardown-to-reuse overview, aggregate trends, and a ranked watch list with source and safety context, distinguishing it from sibling tools.

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?

Clearly states when to use this tool vs. search_salvage_signals for filtered lists, providing explicit alternative.

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.

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