Skip to main content
Glama

Enable country workspace

enable_country_workspace
Idempotent

Enable another delivery country in this account. Admin role required. Starts with zero local-currency balance; existing money stays untouched. Set spending controls independently for this workspace.

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": {
      "country_code": "<country_code>"
    },
    "name": "enable_country_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYes
daily_cap_centsNo
spending_cap_per_delivery_centsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this is a non-read-only, non-destructive, idempotent write, and the description adds meaningful context beyond them: the new workspace starts with zero local-currency balance, existing money is untouched, and spending controls are set independently per workspace. That covers the main state effects an agent would worry about. It does not say what the response looks like or how to undo the change.

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?

Four short sentences, front-loaded with the action and constraint, with no filler. Each sentence carries information, though the ordering could tie the spending-controls note more tightly to the parameters it describes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and 0% schema description coverage on three parameters, the description does well on safety and state effects but leaves the two cap parameters underspecified (units, defaults, null semantics) and omits any return-value expectations. An agent could invoke it correctly for the required country_code but would guess on the optional caps.

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

Parameters5/5

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

The description explicitly notes that spending controls are set independently for this workspace, clarifying the intent of the cap parameters beyond what the 0%-coverage schema provides. However, it never distinguishes daily_cap_cents from spending_cap_per_delivery_cents or explains the cents unit and null meaning.

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?

States a specific verb and resource: "Enable another delivery country in this account." It is clearly the write counterpart to list_country_workspaces, so an agent can distinguish it from the listing sibling without opening a schema. It stops short of explicitly naming the sibling or its inverse operation.

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 gives one concrete prerequisite, "Admin role required," which is genuinely useful for gating the call. However, it never states when not to use it (e.g., when the country is already enabled) or points to the listing tool to check current workspaces first, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.