Skip to main content
Glama

list_business_services

Read-onlyIdempotent

List saved services for the approved business, including pricing text and billing cadence. Pass an ID to look up one saved service.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_business_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuinely new context about what is returned (pricing text and billing cadence) but says nothing about pagination, result limits, or behavior when the ID does not match a saved service.

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 short sentences with no filler, and the primary list behavior is front-loaded ahead of the optional single-record mode. Every clause carries information the agent needs.

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-only tool with no output schema, the description is nearly sufficient: it names the resource, the scope, the returned fields, and the dual mode. Only pagination/result-size expectations and the unknown-ID case are missing.

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 0%, so the description must carry the load; it does explain that the id switches to single-record lookup. It never says which kind of ID is expected (service ID versus business ID) or the failure behavior for an unknown ID, leaving a real ambiguity for the only parameter.

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 uses a specific verb and resource ("List saved services for the approved business") and names the returned fields (pricing text, billing cadence). It also covers the single-record mode. It does not explicitly distinguish itself from the similarly named sibling list_appointment_services, which is the only remaining gap.

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?

"Pass an ID to look up one saved service" gives a usable branch condition for the optional parameter, so the agent knows both modes. However, there is no guidance on when to prefer this over list_appointment_services or get_business_service_area, and no exclusions or prerequisites are stated beyond the vague "approved business".

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