DouxProcess Directory

Get one business

get_business

Read-onlyIdempotent

One business's details: licenses with their basis (issuer_file = matched against the issuer's own published file on checked_at; stated = given by the business, not yet matched, send the person to source_url), contact, whether it takes requests, and its own agent addresses (MCP and A2A).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_business"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The slug from find_businesses.

Output Schema

Name	Required	Description	Default
`city`	No
`luma`	No
`name`	Yes
`note`	No
`page`	Yes
`slug`	Yes
`about`	No
`agent`	No
`phone`	No
`postal`	No
`region`	No
`status`	No
`street`	No
`mcp_url`	No
`website`	No
`licences`	No
`licenses`	No
`languages`	No
`categories`	No
`disclosure`	No
`quote_link`	No
`booking_link`	No
`service_area`	No
`request_contact`	No
`can_take_requests`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / luma

Added value: +{
+  "properties": {
+    "books_online": {
+      "type": "boolean"
+    },
+    "site": {
+      "type": "string"
+    },
+    "site_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "about": {
+      "type": "string"
+    },
+    "agent": {
+      "properties": {
+        "a2a": {
+          "type": "string"
+        },
+        "agent_card": {
+          "type": "string"
+        },
+        "json": {
+          "type": "string"
+        },
+        "markdown": {
+          "type": "string"
+        },
+        "mcp": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "booking_link": {
+      "type": "string"
+    },
+    "can_take_requests": {
+      "type": "boolean"
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "city": {
+      "type": "string"
+    },
+    "disclosure": {
+      "type": "string"
+    },
+    "languages": {
+      "type": "array"
+    },
+    "licences": {
+      "items": {
+        "properties": {
+          "basis": {
+            "enum": [
+              "issuer_file",
+              "stated"
+            ],
+            "type": "string"
+          },
+          "checked_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "classification": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "expires": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "issuer": {
+            "type": "string"
+          },
+          "number": {
+            "type": "string"
+          },
+          "source_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "issuer",
+          "number"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "licenses": {
+      "items": {
+        "properties": {
+          "basis": {
+            "enum": [
+              "issuer_file",
+              "stated"
+            ],
+            "type": "string"
+          },
+          "checked_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "classification": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "expires": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "issuer": {
+            "type": "string"
+          },
+          "number": {
+            "type": "string"
+          },
+          "source_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "issuer",
+          "number"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mcp_url": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "page": {
+      "type": "string"
+    },
+    "phone": {
+      "type": "string"
+    },
+    "postal": {
+      "type": "string"
+    },
+    "quote_link": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    },
+    "request_contact": {
+      "type": "string"
+    },
+    "service_area": {
+      "type": "object"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "seeded",
+        "claimed",
+        "verified"
+      ],
+      "type": "string"
+    },
+    "street": {
+      "type": "string"
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "page"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds valuable domain-specific behavioral context absent from annotations: license basis semantics (issuer_file vs stated), checked_at matching, and the instruction to send people to source_url for unmatched stated licenses. It does not cover error behavior or rate limits, so 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that begins with the resource and then lists field meanings. The nested parenthetical defining license basis is dense but earns its place; slight readability cost keeps it from 5.

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?

Given read-only annotations and an existing output schema, the description need not explain return shape and instead supplies useful field semantics and the trust model for licenses. It omits explicit lookup workflow and not-found behavior, but nothing critical for correct invocation is missing given the schema's documentation.

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 single slug parameter is fully documented in the schema as 'The slug from find_businesses', so the schema does the heavy lifting. The description does not add syntax, format, or validation details beyond what the schema provides, making 3 the appropriate baseline for 100% schema coverage.

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 opens with 'One business's details' and enumerates licenses, contact, request capability, and agent addresses, making the retrieval resource and scope clear. It does not explicitly name sibling tools like find_businesses or verify_business to distinguish itself, so it is clear but not fully sibling-differentiated.

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?

No explicit when-to-use/when-not-use guidance or named alternatives appear in the description. The schema's slug description ('from find_businesses') implies the workflow, and the license-basis instruction provides handling guidance for stated licenses, but tool selection remains inferred rather than stated.

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

All DouxProcess Directory 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?