Skip to main content
Glama

ServiceFront

Try a live demo front desk

tryFrontDesk
Read-only

A live demo for a service business owner: you play a homeowner and chat with a ServiceFront front desk for a made-up example business in one trade, so the owner sees it answer, flag an urgent job and take a lead. Send the homeowner's message; on later turns also send history, the history field of the last result. Every reply is labeled as a demo, nothing is saved, and nobody is paged. Demo turns are limited per day; past the limit you get the written sample conversation instead. Ready trades: plumbing; any other trade says it isn't ready yet. The homeowner is made up too: when the front desk asks for a name, a phone number or an address, give invented ones (a 555 number), never a real person's.

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>",
      "message": "<message>"
    },
    "name": "tryFrontDesk"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeYesThe owner's trade.
historyNoEvery earlier turn of this demo, oldest first: the history field of the last tryFrontDesk result. Leave it out to start a new demo.
messageYesThe homeowner's next message, written the way a homeowner would ask.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only declare read-only, non-open-world, non-idempotent, non-destructive), the description supplies the behavior an agent actually needs: replies are labeled as demo, nothing is persisted, nobody is paged, and turns are rate-limited per day. It also states the fallback output when the limit is hit, which the annotations cannot express.

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?

The opening sentence front-loads what the tool is and who it is for, and every subsequent sentence carries operative information (history chaining, demo labeling, rate limit, trade readiness, invented identities). It is dense and somewhat run-on, but trimming would lose real guidance rather than filler.

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?

With no output schema, the description carries the return-value burden and does so adequately: it says replies are demo-labeled and that an exhausted quota yields the written sample conversation instead, and it references a history field on the result that feeds the next call. A slightly fuller picture of the reply payload would close the remaining gap.

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 real meaning: history must be the history field from the previous result and omitted to start fresh, and message should be phrased as a homeowner would ask. Most valuable, it overrides the nine-value trade enum by declaring only plumbing is ready, which the schema alone would mislead an agent about.

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 definition states a concrete verb-and-resource: it runs a live demo front desk in which the agent plays a homeowner chatting with a simulated service business. It also scopes the audience (service business owner) and the demonstrated behaviors (answering, flagging an urgent job, taking a lead), which no sibling name would convey on its own.

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?

It gives explicit turn-by-turn operating instructions: send the homeowner's message, and on later turns also send history taken from the last result. It names the fallback (the written sample conversation) and the trigger (daily demo limit), and it restricts eligibility to plumbing with an explicit statement of what happens for other trades.

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