Skip to main content
Glama

Accept suggestion

accept_suggestion
Destructive

Accept a translation suggestion: its text becomes the translation of the key in that language. With declineOther, all other active suggestions for the same key and language are declined.

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": {
      "keyName": "<keyName>",
      "languageTag": "<languageTag>",
      "suggestionId": "<suggestionId>"
    },
    "name": "accept_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoOptional: branch name
keyNameYesThe translation key name
namespaceNoOptional: namespace of the key
projectIdNoID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
languageTagYesLanguage tag (e.g. 'de')
declineOtherNoOptional: decline the other active suggestions of this key and language (default false)
suggestionIdYesID of the suggestion (from list_suggestions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description adds real context: accepting promotes suggestion text into the actual translation for that key/language, and declineOther cascades a decline across the other active suggestions. That discloses both the overwrite effect and the collateral side effect, which the annotations alone do not. It stops short of stating permission requirements, reversibility, or what happens to a stale/already-resolved suggestion.

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?

Two sentences, zero padding. The primary effect is front-loaded and the conditional side effect follows in the order an agent needs it.

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 7-parameter mutation with no output schema and fully documented parameters, the description covers the essential what-happens and the conditional cascade. It leaves the agent uninformed about failure modes (suggestion no longer active, missing permission) and whether the overwritten translation is recoverable, which for a destructive tool is a remaining gap.

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?

Schema description coverage is 100%, so the baseline is 3. The description's note that declineOther declines 'all other active suggestions for the same key and language' largely restates the schema's own wording ('decline the other active suggestions of this key and language'), adding little new meaning beyond it.

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 ('Accept a translation suggestion') and then spells out the concrete effect: the suggestion's text becomes the translation of the key in that language. That effect statement separates it from set_translation and decline_suggestion without naming them; explicit sibling naming is the only thing missing.

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?

Usage is only implied: the second sentence describes the declineOther branch, which tells the agent when to set that flag, and the suggestionId schema note points to list_suggestions as the source. There is no explicit statement about when to accept versus decline or versus writing a translation directly, and no prerequisites are called out.

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.