Skip to main content
Glama

Set primary domain

set_primary_domain
Idempotent

Set primary custom domain

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": {
      "domain_id": "<domain_id>"
    },
    "name": "set_primary_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already carry the behavioral profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower, but the description adds nothing. It does not say what happens to the previously primary domain, whether verification is required, or whether the change propagates or takes effect immediately.

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?

Four words, front-loaded and free of padding, but the brevity reflects under-specification rather than efficient communication. Nothing extra is wasted, yet almost nothing useful is conveyed.

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

Completeness2/5

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

This is a mutating, open-world operation on project domain configuration with no output schema and an undocumented required parameter. The definition omits prerequisites, side effects on the prior primary domain, and any indication of what a successful call changes, which is far short of what a state-changing tool needs.

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

Parameters2/5

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

Schema coverage is 50%: project_id is documented in the schema but the required domain_id is a bare string. The description mentions no parameters at all, so it does nothing to compensate for the undocumented required parameter or to clarify what a domain_id refers to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and a resource ('Set primary custom domain'), which is a slight improvement on the bare title. However, it does not explicitly differentiate from siblings like add_domain, remove_domain, or verify_domain, so the agent must infer that 'primary' means promoting an existing domain rather than creating one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite stated (e.g. whether the domain must first be added and verified), and no mention of the alternative tools that operate on domains. The agent is left to guess the ordering of operations.

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.

Resources