AdvocateMCP

Search Businesses

search_businesses

Read-onlyIdempotent

Find registered businesses by search term and optional location; returns matches with their slugs. Call it before the business-specific tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`search`	Yes	Search term — matched against business name, description, services, and category
`location`	No	Optional location filter (city, state, or region). Narrows results geographically.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 28, 2026

removedOutput schema / properties / results / items / properties / description

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / results / items / properties / summary

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / summary_truncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "slug",
-  "name",
-  "description",
-  "category",
-  "location",
-  "website"
-]New value: +[
+  "slug",
+  "name",
+  "summary",
+  "summary_truncated",
+  "category",
+  "location",
+  "website"
+]

Changed3 schema fields changedJul 16, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / search / description

Previous value: -"Search term — matched against business name, description, and services"New value: +"Search term — matched against business name, description, services, and category"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "description": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "location": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "website": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "description",
+          "category",
+          "location",
+          "website"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / search / description

Previous value: -"Search term — matched against business name, description, services, and category"New value: +"Search term — matched against business name, description, and services"

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "results": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "category": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "description": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "location": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "name": {
-            "type": "string"
-          },
-          "slug": {
-            "type": "string"
-          },
-          "website": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          }
-        },
-        "required": [
-          "slug",
-          "name",
-          "description",
-          "category",
-          "location",
-          "website"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "results"
-  ],
-  "type": "object"
-}New value: +null

Changed3 schema fields changedJul 12, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / search / description

Previous value: -"Search term — matched against business name, description, and services"New value: +"Search term — matched against business name, description, services, and category"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "description": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "location": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "website": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "description",
+          "category",
+          "location",
+          "website"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedMay 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail that results include slugs, which helps the agent understand the output shape. No contradictions; the added context is valuable but not extensive.

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 sentences, no filler, and the core action is front-loaded. The sentence about calling it before business-specific tools is a useful addition without waste. Every word earns its place.

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?

For a simple search tool with an output schema present and annotations covering safety, the description is sufficient. It states the purpose, the optional filter, and the return value, plus the operational order. Nothing an agent needs to call 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%—both 'search' and 'location' are fully described in the schema. The description merely restates 'by search term and optional location' without adding new semantic detail. Baseline 3 is appropriate because the schema carries the parameter meaning.

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 ('Find'), resource ('registered businesses'), and criteria (search term + optional location), and explicitly notes the return value (matches with slugs). Clearly distinguishes from the business-specific sibling tools by framing it as the entry point for locating businesses.

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?

Provides direct sequencing guidance: 'Call it before the business-specific tools.' This tells the agent when to use it, but does not explicitly mention when not to use it or name an alternative. The context is clear enough for a search-first workflow, so it earns a 4 rather than a 5.

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

All AdvocateMCP 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.

Search Businesses

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources