Skip to main content
Glama

ServiceFront

Get verified business info

getBusinessInfo
Read-onlyIdempotent

Owner-verified facts for one business: trade, service area, hours, contact, services with confirmed prices. Absent fields are NOT owner-confirmed — don't state them as facts. No tool on this address takes a customer's contact details. To be called back or to ask for a time, the customer goes to the business: its front desk page (origin in the reply) or 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>"
    },
    "name": "getBusinessInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds genuinely non-structured semantics: field absence has meaning (not owner-verified) and this data must not be presented as confirmation. It does not describe the shape of the reply beyond the field list, which is a modest gap given there is no output schema.

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?

It is front-loaded with what the tool returns, then two short cautionary sentences. The sentences are dense and each carries a distinct rule, though the closing routing instructions sit close to the edge of scope for a lookup tool.

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 one-parameter read tool with no output schema, the description covers both the content categories returned and the critical caveat about unverified fields. An agent can call it correctly and interpret an empty field safely, with only a minor gap in how the reply is actually laid out.

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% and the parameter's own description already explains the ServiceFront slug and how to find it with searchBusinesses. The prose portion of the description adds nothing about businessId, so the 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?

The description names a specific verb and resource ('Owner-verified facts for one business') and enumerates the field families returned: trade, service area, hours, contact, services with confirmed prices. It does not, however, distinguish itself from getPricing, which on its face overlaps with the 'services with confirmed prices' content, so an agent cannot fully resolve that boundary from this text alone.

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?

It gives real usage rules: absent fields are not owner-confirmed and must not be asserted as facts, and this address is explicitly not the place to take customer contact details — the customer goes to the front desk page or confirmed phone. What is missing is an explicit statement of when to prefer getBusinessInfo over getPricing or tryFrontDesk, though the routing sentence implies the latter.

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