NomaCMS MCP Server

Official

by NomaCMS

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Set default project locale

set_default_project_locale

Set the project's default locale, automatically adding it to the list if not present. Requires admin API ability.

Instructions

Set the project's default locale. Adds the locale to the list if it was missing. Requires admin API ability.

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": {
      "locale": "<locale>"
    },
    "name": "set_default_project_locale"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	Yes	Locale code to use as default (e.g. en)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description must convey all behavioral traits. It states that the tool 'Adds the locale to the list if it was missing', which is a clear side effect. It also notes the admin requirement. However, it does not detail other behaviors like whether the operation is reversible or what happens to existing data. Adequate but not comprehensive.

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?

The description is two sentences long with no wasted words. The first sentence states the primary action, and the second provides additional behavior and a requirement. It is front-loaded and efficient.

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?

Given the tool's simplicity (single parameter, no output schema), the description covers the purpose, a key behavioral side effect, and a permission requirement. It is complete enough for an agent to understand when and how to invoke it correctly.

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?

The schema already provides a description for the only parameter 'locale' with an example. Schema description coverage is 100%, so baseline is 3. The tool description adds context that the locale will be added to the list if missing, which is more about behavior than parameter semantics. No additional constraints, formats, or use cases are given beyond the schema.

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 the verb 'Set' and the resource 'project's default locale'. It distinguishes itself from the sibling 'add_project_locale' by implying that this both sets as default and adds if missing, whereas the sibling likely just adds without setting as default.

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?

The description mentions 'Requires admin API ability', which provides a precondition for use. However, it does not explicitly state when not to use this tool (e.g., when only adding a locale without setting as default) nor does it name the alternative 'add_project_locale'. Usage is implied but not fully guided.

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