Skip to main content
Glama

1-800Deals Directory

by io.github.cloudalien2025
OverviewDiscussionsAdmin

search_listings

Read-onlyIdempotent

Search 1-800Deals, a national directory of toll-free and vanity-number businesses (water damage restoration, plumbing, pest control, HVAC, garage doors, electricians, roofing). Read-only. Filter by keyword, category and city. Returns public listing fields only: id, name, listing page url, description, address, phone, website, hours and photos. Every search word must match; a query with no matches returns total 0. Use get_listing for one listing's full details.

Input Schema

NameRequiredDescriptionDefault
qNoKeywords, e.g. 'plumber houston' or 'water damage'
areaNoCity, e.g. 'Houston'
pageNoPage number
limitNoMax results (1-50)
categoryNoCategory name or slug from list_categories, e.g. 'Plumbing'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / area
      Added value: +{
+  "description": "City, e.g. 'Houston'",
+  "type": "string"
+}
    • changedInput schema / properties / category / description
      Previous value: -"Category name filter, e.g. 'Restaurants'"New value: +"Category name or slug from list_categories, e.g. 'Plumbing'"
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / q / description
      Previous value: -"Keyword search, e.g. 'plumber' or 'junk removal'"New value: +"Keywords, e.g. 'plumber houston' or 'water damage'"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond them: AND-matching semantics ('Every search word must match') and the empty-result behavior (total 0), plus an explicit enumeration of returned fields.

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?

Front-loads the resource identity, then read-only status, filtering, return fields, matching semantics, and the sibling pointer — a sensible order with little waste. The return-field list is a dense clause, but each part carries information an agent needs.

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 no output schema, the description compensates by enumerating returned fields (id, name, url, description, address, phone, website, hours, photos) and explaining the no-match case. Pagination is covered by the page/limit schema entries, so nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the AND semantics of the q parameter and the fact that category accepts a name or slug sourced from list_categories. The area parameter is described as 'City' in both places with no extra detail.

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?

States a specific verb (Search) and resource (1-800Deals directory), scopes the domain with concrete examples, and explicitly contrasts with the sibling get_listing. An agent can distinguish it from get_listing and list_categories without opening any schema.

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

Usage Guidelines4/5

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

Says to filter by keyword, category and city, and routes the agent to get_listing for a single listing's full details. It does not explicitly state when NOT to use search (e.g. for category enumeration, where list_categories applies), so the routing is clear but not exhaustive.

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

All 1-800Deals Directory toolsInspect
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