Skip to main content
Glama

Choose listing option

optimizer_choose
Idempotent

Select the listing option to ship and define the core phrases it must keep in every locale before localization.

Instructions

Pick the listing option to ship and the core phrases it must carry into every locale. Next step: optimizer_localize.

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": {
      "projectId": "<projectId>",
      "optionId": "<optionId>",
      "corePhrases": "<corePhrases>"
    },
    "name": "optimizer_choose"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionIdYesChosen option id.
projectIdYesProject id (from get_overview).
corePhrasesYesMain-locale phrases to keep in every locale: 1 to 4, the app's main topics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.7
    • changedInput schema / properties / corePhrases / description
      Previous value: -"Main-locale phrases to keep in every locale."New value: +"Main-locale phrases to keep in every locale: 1 to 4, the app's main topics."
    • changedInput schema / properties / corePhrases / maxItems
      Previous value: -50New value: +4
    • changedInput schema / properties / corePhrases / minItems
      Previous value: -0New value: +1
  2. First observedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so safety is covered. The description adds real behavioral context beyond that: the chosen phrases 'must carry into every locale,' disclosing that this selection propagates downstream into localization. It does not say whether an existing selection is overwritten or what happens to already-localized content.

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 short sentences, zero filler, with the action front-loaded and the follow-up step placed after it. Nothing in the text is redundant or padded.

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 three-parameter, fully-documented mutation tool with no output schema, the description covers the action, the payload semantics, and the workflow handoff to optimizer_localize. Minor gaps remain around overwrite behavior and whether localization is mandatory after this call, but an agent has enough 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?

Schema description coverage is 100% and the schema already explains every parameter, including that corePhrases are 'Main-locale phrases to keep in every locale: 1 to 4.' The description's phrase-persistence wording largely restates the schema rather than adding new constraint detail, so the baseline 3 applies.

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?

The description uses a specific verb ('Pick') on a specific resource ('the listing option to ship') plus the secondary payload ('core phrases'). It implicitly separates itself from siblings like optimizer_save_option and optimizer_more_options by framing the action as a final selection 'to ship', though it never names an alternative explicitly.

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 second sentence gives explicit sequencing guidance: 'Next step: optimizer_localize,' which tells the agent this tool is a prerequisite for localization and orders the workflow correctly. It stops short of stating when NOT to use it or how it relates to optimizer_save_option / optimizer_remove_option.

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

Deploy Server

Other Tools