Skip to main content
Glama

ServiceFront

Get an owner-confirmed price

getQuote
Read-onlyIdempotent

The owner-confirmed price for one of a business's services, by service name (ideally a name from getBusinessInfo). grounded:false means no confirmed price exists — never invent one; for an exact quote the customer asks the business on its front desk page (origin in getBusinessInfo) or calls its confirmed phone.

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": {
      "businessId": "<businessId>",
      "service": "<service>"
    },
    "name": "getQuote"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesThe service to price — ideally one of the business's listed service names.
businessIdYesThe business's ServiceFront slug, the first label of its <slug>.servicefront.ai address. Find it with searchBusinesses if you only know the name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description does add real value by disclosing the grounded:false outcome and forbidding fabrication, but it never describes what a successful grounded:true result contains (price, currency, granularity), and there is no output schema to fill that gap.

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?

Purpose is front-loaded and nothing is padding — every clause carries operational meaning (service keying, the grounded flag, the fallback channel). It is written as a dense run-on with em-dashes and parenthetical asides, which costs a little readability.

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?

For a two-parameter lookup with no output schema, the description covers the critical unknown — the ungrounded/absent-price case and what the agent should do then. The main remaining hole is the shape of a positive result, which the agent must discover by calling.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented with slug format and the searchBusinesses lookup path. The description only echoes the 'ideally a name from getBusinessInfo' hint, adding little beyond the structured schema. Baseline 3 applies.

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?

States a specific resource and scope: 'the owner-confirmed price for one of a business's services, by service name'. An agent can tell this is a price-lookup keyed by service, and it points at getBusinessInfo for valid names. It does not explicitly separate itself from the getPricing sibling, so it falls short of a 5.

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?

Gives clear use context and an explicit fallback path: when grounded:false, do not invent a price and instead direct the customer to the front desk page or confirmed phone. That is genuine when/when-not guidance. It stops short of naming when to prefer getPricing or tryFrontDesk instead.

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