Skip to main content
Glama

ServiceFront

Find a business's businessId by name

searchBusinesses
Read-onlyIdempotent

Find a verified ServiceFront business by name (or part of it) and get its businessId for the other tools. Returns up to 5 matches with name, trade, and front-desk URL.

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": {
      "query": "<query>"
    },
    "name": "searchBusinesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe business name, or part of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavior beyond that: results are capped at 5 and each match carries name, trade and front-desk URL, which tells the agent this is a disambiguation aid rather than an exhaustive search. It does not say what to do when the cap is hit or when zero matches return.

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?

Two tight sentences with the action and its downstream purpose front-loaded, followed by the return shape. Nothing is repeated and no sentence could be dropped without losing information.

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 does the work of describing the return value (up to 5 matches with name, trade, front-desk URL), which is exactly what an agent needs to parse results. The remaining gap is edge-case guidance for zero or overflowing result sets, which matters for a lookup tool whose whole job is disambiguation.

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 coverage is 100% and the single 'query' parameter is already documented as 'The business name, or part of it.' The description restates that same idea and adds no new semantics such as the 2-character minimum or how partial matching is interpreted, so the baseline 3 applies.

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 ('Find a verified ServiceFront business by name') and names the concrete output purpose ('get its businessId for the other tools'), which lets an agent place it as the lookup step preceding getBusinessInfo. The scoping word 'verified' further narrows what is returned.

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?

The phrase 'get its businessId for the other tools' clearly implies when to call this (as a prerequisite lookup), and the '(or part of it)' note signals fuzzy matching is acceptable. It stops short of explicit exclusions, e.g. it never says to skip this when a businessId is already known, so an agent must infer that.

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