Skip to main content
Glama
Sign In

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

put_notification_locale

Idempotent

Set locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish locale: { notification_id: "nt_01abc", locale_id: "es", elements: [{ id: "elem_meta_1", title: "Restablecer contraseña" }, { id: "elem_text_1", content: "Haga clic en el enlace para restablecer su contraseña." }] }. The template stays a draft; making it live is a separate step this tool cannot perform.

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": {
      "notification_id": "<notification_id>",
      "locale_id": "<locale_id>",
      "elements": "<elements>"
    },
    "name": "put_notification_locale"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoMust be "DRAFT". These tools cannot publish.
elementsYesArray of element overrides with id and locale-specific content
locale_idYesLocale identifier (e.g. es, fr, pt-BR)
notification_idYesThe notification template ID (nt_ prefix). Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / elements / items / properties / id / description
      Previous value: -"Target element ID to override"New value: +"Target element ID to override, from a prior get_notification or get_notification_draft_content response. Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."
    • changedInput schema / properties / notification_id / description
      Previous value: -"The notification template ID (nt_ prefix)"New value: +"The notification template ID (nt_ prefix). Copy it exactly, character for character, from the response that returned it — never retype it from memory or reconstruct it."
    • changedInput schema / properties / state / description
      Previous value: -"Template state after update"New value: +"Must be \"DRAFT\". These tools cannot publish."
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "DRAFT",
-  "PUBLISHED"
-]New value: +[
+  "DRAFT"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already show readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds meaningful behavioral context beyond this: the operation leaves the template in draft state, and each override must reference an existing element. This helps an agent anticipate side effects and preconditions.

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?

Every sentence serves a purpose: the core action, the precondition about existing element ids, a concrete example, and the draft-state limitation. The example is long but directly clarifies the expected payload shape.

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?

For a mutation tool with no output schema, the description covers the critical context: what the tool does, the draft behavior, and the element-reference rule. The required state parameter is described in the schema, and the example covers the remaining ambiguity around the elements array.

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 description coverage is 100%, so the schema already documents each parameter. The description adds value through a concrete example that clarifies the elements array structure (id, title, content), which is otherwise left open via additionalProperties.

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 leads with a specific verb and resource: 'Set locale-specific content overrides for a V2 notification template.' This clearly distinguishes the tool from siblings like put_notification_content or put_notification_element, and the draft caveat separates it from publish actions.

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

Usage Guidelines4/5

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

The description gives a clear when-to-use context ('locale-specific content overrides') and an explicit exclusion: 'The template stays a draft; making it live is a separate step this tool cannot perform.' However, it does not name the alternative tools for non-locale overrides or publishing, so guidance is not fully explicit.

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

All Courier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources