Skip to main content
Glama

decision_choice

Selects one option from 2–255 choices using multimodal input and returns the chosen result, confidence score, and probability distribution.

Instructions

Select one option from a defined set of 2 to 255 choices over multimodal input. Returns selected choice, confidence, and probability distribution.

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": {
      "state": "<state>",
      "instructions": "<instructions>",
      "criteria": "<criteria>"
    },
    "name": "decision_choice"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNogemini-decision-1
stateYes
api_keyNo
criteriaYes
question_idNochoice
instructionsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It mentions multimodal input and names the return fields, but says nothing about authentication (an api_key parameter exists), cost/latency, what happens when no choice reaches a threshold, or how the model behaves on ambiguous criteria, leaving the significant behavioral questions unanswered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the operation and its bound, with no filler. The second sentence restates return values that the output schema already supplies, which is the only wasted content.

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?

Given six undocumented parameters, nested-object inputs, and no annotations, the definition is thin. The output schema covers the return shape, but the description leaves the input contract and the behavior of the tool almost entirely unexplained for a decision-making operation.

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 description coverage is 0% across six parameters with three required, so the description must compensate and it largely does not. 'A defined set of 2 to 255 choices' hints that the criteria object enumerates options, but state, instructions, model, api_key, and question_id receive no explanation anywhere.

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 gives a specific verb and resource ('Select one option from a defined set of 2 to 255 choices') plus the input modality ('over multimodal input'), which is far more informative than the bare name decision_choice. It does not, however, distinguish this tool from nearby siblings such as decision_evaluate or decision_score, so an agent gets no help choosing among them.

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 or when-not-to-use guidance, and no alternative is named. The only constraint offered is the 2-to-255 choice cardinality, which implicitly bounds inputs but says nothing about which tool to reach for, so an agent must infer usage from the name alone.

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