Skip to main content
Glama

jev_choice

Select one option from 2 to 255 choices over multimodal input and return the selected choice, confidence, and probability distribution for informed decisions.

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": "jev_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 bears the full behavioral burden, and it mostly does not meet it. It mentions multimodal input and return contents (choice, confidence, probability distribution), but says nothing about authentication despite an api_key parameter, nothing about the model being selectable, cost/latency, or what happens if the choice set is malformed or out of the 2-255 range. Return-value disclosure is largely redundant because an output schema exists.

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 tight sentences with the core capability front-loaded and the return contract second; nothing is padded. It is arguably too short rather than too long, but that is a completeness problem, not a wording one.

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?

This is a complex tool: six parameters, nested objects, required instructions/criteria/state, and an api_key. With zero schema coverage and no annotations, the description leaves the agent guessing about how to construct the required arguments, making it inadequate for the tool's complexity. The existence of an output schema excuses omitting return details, but nothing else.

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 (state, instructions, criteria, model, api_key, question_id), so the description must compensate and does not. It never explains what state, instructions, or the criteria map mean, nor that criteria likely defines the candidate options; the only related hint is the '2 to 255 choices' bound, which is not tied to any parameter.

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 states a specific verb and resource: 'Select one option from a defined set of 2 to 255 choices over multimodal input.' That is far more informative than the bare name jev_choice and bounds the operation's scope. It does not, however, distinguish itself from siblings such as jev_evaluate, jev_score, or decision_choice, so an agent cannot tell from this text alone which of the near-identical names to pick.

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 phrase 'defined set of 2 to 255 choices' implies a pre-enumerated option scenario, but the description never says how that contrasts with the evaluate/score siblings or what input shape constitutes 'choices'.

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