Skip to main content
Glama

ServiceFront

Sample front-desk conversation for a trade

sampleConversation
Read-onlyIdempotent

A sample conversation between a homeowner and a ServiceFront front desk in one trade: the question, the answer, urgency triage, and the captured lead. The business in it is a made-up example. Ready trades: plumbing; any other trade says it isn't ready yet and returns a ready trade's sample as a labeled stand-in.

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": {
      "trade": "<trade>"
    },
    "name": "sampleConversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeYesThe owner's trade.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context. It does so with two non-obvious traits: the business in the sample is fabricated, and non-plumbing trades do not fail but return a labeled stand-in from a ready trade — a substitution behavior an agent would otherwise misreport.

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?

Three tight sentences: what the artifact contains, its fabricated-data caveat, then the trade-availability rule up front. Each sentence carries distinct information, though the availability rule is buried after the caveat rather than leading with it.

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?

For a single-parameter, read-only tool with no output schema, the description covers what is returned, that the data is synthetic, and the one behavioral edge case (unsupported trade). Nothing an agent needs in order to call it or interpret the result correctly is missing.

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% and the enum already lists all nine trades, so the baseline is 3. The description earns a bump by revealing that only "plumbing" yields a native sample and every other enum value returns a labeled stand-in, which is meaning the schema cannot convey.

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?

"A sample conversation between a homeowner and a ServiceFront front desk in one trade" states a specific artifact, and the clause "the question, the answer, urgency triage, and the captured lead" enumerates its parts. It is clearly not a live interaction tool, distinguishing it in spirit from tryFrontDesk, but it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description explains the per-trade behavior and the fallback for unsupported trades, which implicitly tells the agent what to expect when calling it. It does not state when an agent should pick this over tryFrontDesk or aboutServiceFront, so the choice between siblings is left to inference.

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