Skip to main content
Glama
Sign In

dfwmetro.net directory

by io.github.cexplayer01
OverviewDiscussionsAdmin

find_listings

Read-onlyIdempotent

Find service businesses in the dfwmetro.net directory for booking. Returns every listing with its verification status labeled: VERIFIED businesses (human verification-desk reviewed) rank first and carry machine-booking capability and endpoint health; NOT_YET_VERIFIED businesses are clearly labeled, ranked by automated pre-check score, and carry machine_ready:false. Pass verified_only:true for the strict VERIFIED-only shelf. This tool can never change verification status.

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_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoDFW city filter, e.g. 'Plano'.
limitNoMax listings to return (1-50).
tradeNoCategory id from https://dfwmetro.net/categories.json, e.g. 'plumbing'. Legacy display labels ('Plumbing', 'Heating & Air Conditioning', 'Electrical') are also accepted and normalized.
subcategoryNoSubcategory label filter, e.g. 'Drain cleaning'.
verified_onlyNoTrue 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.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry the read-only, idempotent, non-destructive, closed-world safety profile. The description adds genuinely new behavioral context beyond them: verification-status labeling and ranking rules, the meaning of trust_level 'pending' and machine_ready:false, endpoint health on verified listings, and the explicit guarantee that it can never change verification status. It stops short of describing pagination or response size beyond limit.

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 purpose, then the verification ranking explanation, then the strict-shelf instruction. The middle section is dense but each clause carries semantic weight (rank order, trust_level meaning, machine_ready flag). Minor redundancy with the schema's verified_only description, but no filler sentences.

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

Completeness3/5

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

A read-only discovery tool with a rich 5-parameter schema and full annotations, but no output schema. The description never conveys the response shape, how limit interacts with ranking, or what fields accompany each listing beyond labels, leaving structure to inference. Adequate for invocation but incomplete for understanding results.

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 description coverage is 100%, so baseline is 3; the description earns above that by explaining the semantic intent of verified_only (the 'strict premium shelf') and the ranking consequence of the other parameters' filters. It reinforces rather than merely repeats the schema for the most decision-relevant flag.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Find service businesses in the dfwmetro.net directory for booking.' It also distinguishes the default ranked-all behavior from the strict VERIFIED-only shelf via verified_only:true, though it does not explicitly name the sibling tool find_verified_listings as an alternative, leaving that differentiation implicit rather than explicit.

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?

Explains the default mode (all listings returned with verification status labeled, VERIFIED ranked first) and the condition that selects the strict variant (verified_only:true). It does not explicitly name when to prefer find_verified_listings or state prerequisites, but the routing decision is clearly derivable from the default/strict framing.

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 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