HireLocksmiths — Locksmith Finder

request_quote

Create a lead: ask a specific locksmith for a quote.

ONLY call this when the user has chosen a provider and wants to be contacted —
it sends a real request to the locksmith. Provide a phone (preferred) or email
so the locksmith can reach the customer. Returns a reference id (HL-####); the
locksmith confirms availability, price, and ETA directly.

Args:
    locksmith_id: id from search_locksmiths / get_locksmith.
    name:         Customer name.
    phone:        Customer phone (preferred). Phone OR email is required.
    email:        Customer email (alternative to phone).
    zip:          5-digit ZIP of the job (improves routing/records).
    service:      Job type, e.g. "lockout", "automotive".
    details:      Free-text description of the job.
    urgency:      e.g. "emergency", "today".

Input Schema

TableJSON Schema

Name	Required	Default
`zip`	No
`name`	Yes
`email`	No
`phone`	No
`details`	No
`service`	No	lockout
`urgency`	No
`locksmith_id`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool sends a real request to the locksmith and returns a reference ID (HL-####), with the locksmith confirming availability/price/ETA directly. This provides adequate transparency for an agent.

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?

The description is concise yet informative, with a clear structure: overall purpose, usage constraint, outcome, then parameter list. Every sentence adds value, and key info is front-loaded.

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?

Given 8 parameters and no output schema, the description covers inputs meaningfully and mentions the return value (reference id). It does not discuss error cases or idempotency, but is otherwise complete for this type of lead creation 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 description coverage is 0%, but the description adds comprehensive parameter semantics: required fields (locksmith_id, name), phone/email requirement ('Phone OR email is required'), and examples for service and urgency. This fully compensates for the schema gaps.

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 creates a lead by asking a specific locksmith for a quote. It uses specific verb-resource ('Create a lead', 'ask for a quote') and distinguishes from siblings like 'book_job' (post-quote) and 'get_locksmith' (information retrieval).

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?

The description explicitly states 'ONLY call this when the user has chosen a provider and wants to be contacted', providing clear when-to-use guidance. It lacks explicit when-not-to-use or alternatives, but the context is sufficient given sibling names.

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?