HireLocksmiths — Locksmith Finder

search_locksmiths

Find vetted, licensed locksmiths near a location.

Use this first when a user needs a locksmith. Returns a ranked list of
human-vetted providers (featured first) with id, name, city, services,
rating, verified/featured flags, phone, and a profile URL.

Args:
    location: A 5-digit US ZIP code (preferred) or a US city name.
    service:  Optional job type, e.g. "lockout", "automotive", "residential",
              "commercial", "rekey", "install", "safe".
    urgency:  Optional, e.g. "emergency", "today", "scheduled".
    budget:   Optional free-text budget hint.
    limit:    Max results to return (1-20, default 5).

Note: price and ETA are NOT pre-listed — they are confirmed by the locksmith
after you call request_quote. Do not invent prices or ETAs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`budget`	No
`service`	No
`urgency`	No
`location`	Yes

TDQS

A4.8/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses results are human-vetted, featured first, and price/ETA are not pre-listed. Lacks mention of rate limits or auth, but sufficient for this tool.

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?

Concise yet comprehensive. Purpose, return fields, parameter descriptions, and a key note are all included in a clear, structured format without redundancy.

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?

No output schema, but description lists all returned fields (id, name, city, services, rating, flags, phone, profile URL) and states what is NOT included. Complete for a search tool.

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

Parameters5/5

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

Schema coverage is 0%, but description adds detailed explanations for all 5 parameters: location format, service examples, urgency examples, budget hint, limit range/default.

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 tool's purpose: find vetted, licensed locksmiths near a location. It distinguishes from siblings like get_locksmith (single provider) and request_quote (for quotes).

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 says 'Use this first when a user needs a locksmith' and advises not to invent prices/ETAs, guiding the agent to use request_quote for those details.

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

All HireLocksmiths — Locksmith Finder 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.3/5.0

Disambiguation3/5

Some tools overlap: check_availability and get_eta return nearly identical coverage info, and book_job/request_quote serve similar but distinct purposes. Descriptions help differentiate, but ambiguity remains.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., book_job, check_availability, get_eta), making them predictable and easy to understand.

Tool Count5/5

With 6 tools covering search, profile, availability, quotes, and booking, the count is well-scoped for a locksmith finder service without being excessive or insufficient.

Completeness4/5

Core workflows (search, view profile, check availability, request quote, book) are covered. Missing features like cancel/update bookings are minor but notable gaps.

Resources

Need Help?