Ni Biashara Diaspora Directory

Search diaspora businesses

search_directory

Read-onlyIdempotent

Keyword search of the Ni Biashara directory of African and Caribbean diaspora businesses in the US, Canada and beyond, optionally filtered by city, metro and category. Listings are compiled from public sources.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_directory"
  }
}

Input Schema

Name	Required	Description
`q`	No	Business name, service or keywords, e.g. 'catering' or 'ethiopian restaurant'
`city`	No	City, e.g. 'Houston'
`limit`	No	Maximum results (default 20)
`metro`	No	Metro, e.g. 'DFW'
`category`	No	Category, e.g. 'Catering & Events'

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful provenance ("compiled from public sources") and directory scope, but does not disclose result ordering, pagination, or any limitations beyond that.

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 tight sentences with no filler: the core search behavior and filters come first, followed by a short provenance note. Every sentence earns its place.

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?

For a five-parameter search tool with full schema coverage and safety annotations, the description gives adequate scope, filters, geography, and provenance. It leaves minor gaps around result contents and pagination, but nothing critical for correct invocation.

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%, so the schema already documents q, city, metro, category, and limit with examples and defaults. The description adds only that these filters are optional, which the schema also communicates, 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 uses a specific verb ("Keyword search") and resource ("Ni Biashara directory of African and Caribbean diaspora businesses"), and states geographic scope plus optional filters. This is far more specific than tautology and lets an agent identify the tool's exact purpose.

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?

Usage is implied by the keyword-search framing and the mention of optional city, metro, and category filters. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives to route against.

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

All Ni Biashara Diaspora 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?