Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

getTopCategory

Read-onlyIdempotent

Retrieve a single top-level category by its profession ID. Returns the category name, filename, and, optionally, full SEO metadata.

Instructions

Get a single category - Fetch a single TOP-level member category by profession_id. Read-only.

Lean by default: keeps profession_id, name, filename. Strips SEO metadata. Pass include_category_schema=1 to restore.

A Top Category is the highest level of the 3-tier member classification. Backed by BD's list_professions table.

Use when: you already have a profession_id and need its full record (name, filename, etc.). For enumeration use listTopCategories.

Required: profession_id (path parameter).

See also: listTopCategories (enumerate), listSubCategories (sub-categories under this one; filter by profession_id).

Returns: { status: "success", message: [{...record}] } - array of 1 record with full fields.

How a member gets classified on their public profile:

  • users_data.profession_id -> points at a single Top Category (the member's primary classification; shown in URL slug)

  • users_data.services -> CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)

  • rel_services rows (Member ↔ Sub Category links) -> used when you need per-link metadata like avg_price, specialty, num_completed. Optional; most sites use just the CSV field.

Sub-sub-categories: createSubCategory with master_id=<parent service_id> creates a Sub Category nested under another Sub Category (a "sub-sub"). master_id=0 (default) means the Sub Category sits directly under a Top Category (the profession_id).

There is NO createProfession or createService tool in this MCP — those are BD's internal table names. Use createTopCategory / createSubCategory instead (BD's table-name → tool-name mapping is documented in Rule: Table to endpoint).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profession_idYes
include_category_schemaNoOpt in to restore full category metadata: `desc` (SEO description), `keywords`, `image`, `icon`, `sort_order`, `lead_price`, `revision_timestamp`. Default lean keeps: category ID + `name` + `filename` + hierarchy links (`profession_id` on top/sub, `master_id` on sub for sub-sub parent). Hierarchy is always visible so agents can traverse top -> sub -> sub-sub without opt-in.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds rich detail: default lean response, opt-in for full metadata via include_category_schema, return format, and background on member classification. No contradiction with annotations.

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

Conciseness3/5

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

Well-organized with clear sections, but verbose. Contains extensive background on member classification and relation tables that is not essential for tool invocation. Could be more concise while retaining key points.

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?

Comprehensive given no output schema: specifies return format, default vs full response, required parameter, usage context, and related tools. Covers all necessary information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema documents both parameters, but description adds significant meaning: explains 'lean by default' and lists fields restored by include_category_schema. Provides context beyond schema for profession_id (path parameter). Schema coverage is 50%, but description compensates well.

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?

Clearly states the verb (get/fetch), resource (top-level member category), and key identifier (profession_id). Differentiates from siblings listTopCategories and listSubCategories by specifying scope and use case.

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?

Explicitly states when to use ('when you already have a profession_id') and when not to ('For enumeration use listTopCategories'). Provides clear alternatives and context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brilliantdirectories/brilliant-directories-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server