Skip to main content
Glama

AdvocateMCP

by com.advocatemcp

List Services

list_services
Read-onlyIdempotent

Lists the services a business has configured, with their prices and the exact arguments to quote each one. Call this BEFORE get_quote: the service name must match a configured service, and only a service marked payable returns an exact price with the offer_id that get_payment_handoff_url requires. Quoting a name that is not on this list silently falls back to an estimate with no offer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesBusiness slug identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
servicesYes
guidance_for_agentYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds valuable behavioral context: only payable services return an exact price with an offer_id, and incorrect quoting silently falls back to an estimate with no offer. This is not present in annotations.

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?

Three sentences pack essential information with no fluff: what it does, when to call it, and key behavioral caveats. Each sentence earns its place and the structure front-loads the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description need not explain return values. It covers the prerequisite relationship with get_quote, the payable/offer_id distinction, and the fallback behavior, making it complete for this tool.

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?

The schema already fully describes the single parameter 'slug' as a business slug identifier (100% coverage). The description does not add extra semantics to the parameter itself, so baseline 3 is appropriate.

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 description explicitly states the tool lists services with prices and quoting arguments, and distinguishes it from siblings by referencing get_quote and get_payment_handoff_url. This gives a specific verb+resource+scope.

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 explicitly says 'Call this BEFORE get_quote' and explains when to use it (to get exact prices for payable services) and the consequence of not doing so (silent estimate fallback). This is clear when-to-use and when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdvocateMCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct action or resource: searching, quoting, reserving, confirming, payment handoff, callback, subscription, and business queries. Even related tools like reserve_slot and confirm_booking have clearly separated roles (holding vs. claiming). No overlapping purposes or ambiguous boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_businesses, get_quote, reserve_slot, confirm_booking). The verbs are varied but each is intuitive and fits the action. There are no mixed naming conventions or vague verb choices.

Tool Count5/5

13 tools cover the core booking and business-intelligence workflow without redundancy. The scope is well-defined—discovery, pricing, reservation, confirmation, payment, handoff, and subscription—so each tool earns its place. Not too thin, not overloaded.

Completeness3/5

The surface covers search, pricing, reservation, confirmation, payment, and handoff, but missing explicit cancellation or modification tools for bookings. A user asking to cancel a reservation would have no direct tool; get_cancellation_policy only provides text. Also no way to list a customer's existing bookings. This leaves notable gaps for a booking-focused server.

Resources