Skip to main content
Glama

Snap: choice question

snap_choice

Ask Snap to choose one labeled option from 2-255 for a given state, returning the pick, a confidence score, and a probability for every option.

Instructions

Ask SubQ's Snap decision model a single Choice question: pick one of 2-255 labelled options for a state. Returns the chosen option, a confidence value, and a probability for every option, under the question name "answer".

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>",
      "options": "<options>"
    },
    "name": "snap_choice"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOptional Snap model id override (default: subq-snap-1.2).
stateYesThe situation to decide about: text, a JSON object, or a JSON array.
imagesNoUp to 4 images for this request. PNG, JPEG, or WebP, base64-encoded with no data: prefix; at most 4 MiB decoded each, 8 MiB in total. Every question in the request sees every image.
optionsYesObject mapping each option label to a description (string, structured object/array, or null; 2-255 options).
instructionsYesWhat Snap should decide: plain-language text, or structured JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / model / description
      Previous value: -"Optional Snap model id override (default: subq-snap-1.1)."New value: +"Optional Snap model id override (default: subq-snap-1.2)."
  2. Changed6 schema fields changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / images / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / instructions / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / options / additionalProperties / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / options / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / state / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  }
      +]
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 usefully discloses the return shape (chosen option, confidence, per-option probabilities keyed under "answer"), but says nothing about cost, latency, auth needs, determinism, or whether repeated calls with the same state are stable.

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: the operation and its constraint first, the return contract second. No filler, though the return sentence could be trimmed slightly and the options range repeats the schema.

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 nested-object, five-parameter inference tool with no output schema, the description covers the essential contract and the return structure. It leaves the images and model-override parameters entirely to the schema, which is acceptable given 100% schema coverage but is a small gap for a multimodal tool.

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 schema already documents all five parameters including the model override, images, and the state/options unions. The description adds only the options count range and the notion of a 'state', so it does not exceed the baseline set by a fully documented schema.

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 ('Ask SubQ's Snap decision model a single Choice question') plus the cardinality constraint (2-255 labelled options). It characterizes the operation as a single-question choice task, which implicitly distinguishes it from a general decide/score sibling, but it never names those siblings to make the boundary explicit.

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 context is only implied by 'single Choice question' and 'for a state' — an agent can infer this is for one pick-one-of-N decision, but there is no statement of when to prefer it over snap_decide, snap_score, or snap_noul, and no prerequisites or exclusions are given.

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