Advocate

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

Name	Required	Description	Default
`slug`	Yes	Business slug identifier

Output Schema

Name	Required	Description	Default
`slug`	Yes
`services`	Yes
`guidance_for_agent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 24, 2026
- removedOutput schema / properties / services / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / services / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / services / items / properties / price_max_cents / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / services / items / properties / price_max_cents / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / services / items / properties / price_min_cents / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / services / items / properties / price_min_cents / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / services / items / properties / unit / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / services / items / properties / unit / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedAug 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), but the description adds genuinely non-obvious behavior: an unlisted service name 'silently falls back to an estimate with no offer,' and only payable services return an offer_id. This is the kind of silent-failure disclosure an agent cannot infer from structured fields. It stops short of describing empty-list or error cases.

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, each load-bearing: what it returns, when to call it, and the consequence of getting it wrong. The imperative ordering cue is front-loaded in the second sentence where the agent will act on it.

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?

An output schema exists, so return shape is already covered, yet the description still highlights the fields that matter for chaining (price, offer_id, payable flag). Combined with the one-parameter schema and read-only annotations, nothing needed to invoke it correctly is 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 100% and the single 'slug' parameter is documented in the schema, so the baseline of 3 applies. The description never mentions the slug or its format, adding no meaning beyond the schema.

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 ('Lists the services a business has configured') and specifies what each entry contains: prices and the exact arguments for quoting. It is clearly distinguishable from siblings like get_quote, which it explicitly names as the downstream consumer.

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?

Gives explicit ordering guidance ('Call this BEFORE get_quote') plus the condition that makes it necessary: the service name must match a configured service and be marked payable. The alternative path (quoting an unlisted name) is spelled out, so the agent knows both when to use this and what happens if it skips it.

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

All Advocate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?