Skip to main content
Glama

Delco Plumber Now

chat_with_delco_plumber_now

Multi-turn chat with the Delco Plumber Now assistant in plain language: ask questions, get a typical price range, and get the person connected with a local plumber. Pass the conversation_id from the previous reply to continue. When the person agrees to be contacted and shares a phone or email, the reply includes ready_to_submit with their details; submitting is done separately with request_contact. Use this for open-ended questions; use the single-purpose tools when you only need coverage, a price range or the phone number. Returns JSON with the reply, the conversation_id and call/text links; up to 30 messages per conversation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "chat_with_delco_plumber_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesWhat the person (or you, on their behalf) wants to say or ask, in plain words, up to 2000 characters
conversation_idNoFrom the previous reply (c_ plus 16 hex characters); omit to start a new conversation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"From the previous reply; omit to start"New value: +"From the previous reply (c_ plus 16 hex characters); omit to start a new conversation"
    • addedInput schema / properties / message / description
      Added value: +"What the person (or you, on their behalf) wants to say or ask, in plain words, up to 2000 characters"
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds the context they cannot: that a contact handoff surfaces as ready_to_submit and must be submitted separately via request_contact, that the reply carries call/text links, and that conversations are capped at 30 messages. That is exactly the non-obvious behavior an agent needs before calling.

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?

Five sentences, each carrying distinct information — capability, continuation, handoff contract, sibling routing, return shape plus limit. Front-loaded with the purpose, with no repetition of schema fields.

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?

There is no output schema, yet the description names the return fields (reply, conversation_id, call/text links) and the conditional ready_to_submit payload, plus the 30-message ceiling. For a two-parameter conversational tool, an agent has everything needed to call it and interpret the reply.

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 conversational semantics the schema cannot: conversation_id exists to continue an existing thread and is omitted to start a new one, and the state of that thread determines whether ready_to_submit appears. Slight uplift over the schema-only baseline.

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 — 'multi-turn chat with the Delco Plumber Now assistant' — and immediately scopes what the chat can do (ask questions, price range, connect to a plumber). It names its siblings' roles, so an agent can distinguish it from check_coverage, get_price_range, get_contact_info and request_contact 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 Guidelines5/5

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

Explicit routing: 'Use this for open-ended questions; use the single-purpose tools when you only need coverage, a price range or the phone number.' It also gives the continuation rule (pass conversation_id from the previous reply) and flags that this tool does not submit contact details — that is request_contact's job.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources