dfwmetro.net directory

find_verified_listings

Read-onlyIdempotent

Find VERIFIED service businesses in the dfwmetro.net directory for booking. Only listings that passed human verification-desk review are returned — this tool can never surface unverified businesses and can never change verification status. Each result includes the business's booking_url plus machine-booking capability and endpoint health when known. Use booking_url for human-style booking flows; use capability endpoints only when present. Kept for backward compatibility; new integrations should prefer find_listings with verified_only:true.

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": "find_verified_listings"
  }
}

Input Schema

Name	Required	Description
`city`	No	DFW city filter, e.g. 'Plano'.
`limit`	No	Max listings to return (1-50).
`trade`	No	Category id from https://dfwmetro.net/categories.json, e.g. 'plumbing'. Legacy display labels ('Plumbing', 'Heating & Air Conditioning', 'Electrical') are also accepted and normalized.
`subcategory`	No	Subcategory label filter, e.g. 'Drain cleaning'.
`verified_only`	No	True returns only VERIFIED listings (the strict premium shelf); false (default) returns all listings with verification status labeled, VERIFIED ranked first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior3/5

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

The description adds real value beyond the readOnly/idempotent/non-destructive annotations by stating invariants (cannot change verification status) and return content (booking_url, capability, endpoint health), which matters since there is no output schema. However, the flat claim that 'this tool can never surface unverified businesses' conflicts with the tool's own schema, where verified_only defaults to false and unverified listings are returned and labeled.

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-loaded with the core purpose, then the verification guarantee, then per-result contents, then the booking guidance and deprecation note. Dense but every sentence carries information; the only minor cost is that the backward-compatibility note trails at the end where it is easy to skim past.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, read-only discovery tool with no output schema, the description covers return shape, verification semantics, and the migration path to find_listings. Its one substantive gap is that it does not reconcile the 'never surfaces unverified businesses' claim with the verified_only default, leaving the caller with a wrong mental model of the primary filter.

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

Parameters2/5

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

Schema description coverage is 100%, so baseline would be 3, but the description actively muddies the key parameter: it asserts unverified businesses can never be returned, while the schema documents verified_only default false as returning all listings with status labeled. An agent reading only the description would mis-set verified_only semantics; the other parameters (city, trade, subcategory, limit) get no added meaning.

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 and resource ('Find VERIFIED service businesses in the dfwmetro.net directory') plus the scope constraint (human verification-desk reviewed only). It also names the sibling replacement path (find_listings with verified_only:true), so an agent can distinguish it from find_listings and submit_listing without opening a schema.

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 routes usage: 'Use booking_url for human-style booking flows; use capability endpoints only when present', and 'new integrations should prefer find_listings with verified_only:true' for a backward-compatibility migration path. Both the when-to-use and the when-to-use-something-else conditions are stated.

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

All dfwmetro.net directory 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.