Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateCountry

Idempotent

Update a country record to enable or disable it on your site by toggling its active status. Only send the fields you want to change.

Instructions

Update a country (corrections / active toggle) - Update a country record. Read-mostly - primary use is toggling active to enable/disable a country on the site. Fields omitted are untouched (PATCH semantics - only send what you want to change).

Required: country_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_idYes
country_codeNoISO 3166-1 alpha-2 (e.g. `US`, `CA`, `GB`)
country_nameNo
activeNo
_clear_fieldsNoColumn names to clear to empty string. Available on every `update*` operation. Works on base columns AND EAV/`users_meta` rows (rows preserved with `value=""`). To actually clear a field you MUST use this parameter — sending the field with `""` alone is a no-op (BD drops empty values). To remove a `users_meta` row entirely, use `deleteUserMeta`. See **Rule: Clearing fields**. Example: `_clear_fields: ["h2", "hero_link_url"]`.
Behavior4/5

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

Discloses PATCH semantics, Read-mostly nature, and the `_clear_fields` behavior. This adds value beyond annotations which provide idempotentHint and openWorldHint but no details.

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 succinct with front-loaded purpose and key details. Bold for required parameter aids readability.

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?

Explains PATCH semantics, primary use, and the `_clear_fields` mechanism. No output schema, but the description is adequate for an update operation.

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?

Description mentions `country_id` is required and `active` as primary toggle, but does not add meaning for `country_code` or `country_name`. With 40% schema description coverage, the description compensates partially.

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 'Update a country (corrections / active toggle)' and specifies the primary use is toggling `active`. It distinguishes this from other tools by naming the resource and action.

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?

It provides context about when to use (primary use is toggling active) and PATCH semantics, but lacks explicit exclusions or comparison to sibling update tools like updateCity or updateState.

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