AdvocateMCP

Get Business Credentials

get_credentials

Read-onlyIdempotent

Returns the business's self-reported licenses, insurance, bonding, and certifications. Use this for trust-sensitive verticals (contractors, healthcare, legal, locksmiths) when a user asks 'are they licensed?' or 'are they insured?'. The response carries explicit 'self-reported' framing so agents don't upgrade tenant claims to verified facts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Business slug identifier

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes
`bonded`	Yes
`insured`	Yes
`summary`	Yes
`licenses`	Yes
`certifications`	Yes
`has_credentials`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 16, 2026

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

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "bonded": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "certifications": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "has_credentials": {
+      "type": "boolean"
+    },
+    "insured": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "licenses": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "expires_at": {
+            "type": "string"
+          },
+          "jurisdiction": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "number": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "has_credentials",
+    "licenses",
+    "insured",
+    "bonded",
+    "certifications",
+    "summary"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 12, 2026

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

changedInput schema / properties / slug / description

Previous value: -"Business slug identifier"New value: +"business slug"

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "bonded": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "certifications": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "has_credentials": {
-      "type": "boolean"
-    },
-    "insured": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "licenses": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "expires_at": {
-            "type": "string"
-          },
-          "jurisdiction": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "number": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "name"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "slug": {
-      "type": "string"
-    },
-    "summary": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "slug",
-    "has_credentials",
-    "licenses",
-    "insured",
-    "bonded",
-    "certifications",
-    "summary"
-  ],
-  "type": "object"
-}New value: +null

Changed3 schema fields changedJul 12, 2026

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

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "bonded": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "certifications": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "has_credentials": {
+      "type": "boolean"
+    },
+    "insured": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "licenses": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "expires_at": {
+            "type": "string"
+          },
+          "jurisdiction": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "number": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "has_credentials",
+    "licenses",
+    "insured",
+    "bonded",
+    "certifications",
+    "summary"
+  ],
+  "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 indicate read-only, non-destructive, idempotent behavior. The description adds critical context: the response is 'self-reported' and agents should not upgrade claims to verified facts, which is valuable beyond the 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?

Two concise sentences: first states purpose, second provides usage guidelines and key behavioral note. No filler or redundancy; every sentence adds value.

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 tool's simplicity (one parameter, output schema present, read-only), the description covers purpose, usage context, and critical behavioral nuance completely. No gaps remain.

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% with a description for the only parameter (slug). The description does not add additional parameter semantics beyond what the schema provides, 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 clearly states the tool returns business credentials (licenses, insurance, etc.) and uses specific verbs. It is easily distinguishable from sibling tools like get_availability or get_cancellation_policy which cover different aspects.

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?

Explicitly recommends use for trust-sensitive verticals and gives example user queries ('are they licensed?'). While it lacks explicit 'do not use' statements, the guidance is clear and actionable.

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.

Get Business Credentials

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources