Skip to main content
Glama

Snap: decide (typed questions over a state)

snap_decide

Ask a decision model typed choice, score, or true/false questions about text, JSON, or up to four images and get probabilistic answers for routing, triage, moderation, and risk scoring.

Instructions

Ask SubQ's Snap decision model one or more typed questions (choice, score and/or noul) about a state in a single call. Returns typed answers with probabilities. The state may be text or structured JSON, and up to 4 images may accompany it; every question sees the state and every image.

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>",
      "questions": "<questions>"
    },
    "name": "snap_decide"
  }
}

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.
questionsYesMap of question name (up to 100 characters) to typed question; 1-128 questions. Each question has a type (choice | score | noul), instructions, and criteria: choice = object of option label -> description (string, structured object/array, or null; 2-255 options); score = array of 2-10 ordered level descriptions; noul = optional object of true/false descriptions. Instructions may be 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
    • removedInput schema / properties / questions / additionalProperties / additionalProperties
      Removed value: -false
    • changedInput schema / properties / questions / additionalProperties / required
      Previous value: -[
      -  "type"
      -]New value: +[
      +  "type",
      +  "instructions"
      +]
    • addedInput schema / properties / questions / 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.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the call returns typed answers with probabilities and that every question sees the state and every image, but it omits return shape details, error behavior, permissions, and cost or rate-limit context.

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?

The description is two tight sentences, front-loaded with the core purpose and follow-on behavioral details. Every sentence contributes useful information without repetition or unnecessary wording.

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?

The input schema is rich and fully covers the parameters, so the description does not need to repeat all constraints. It covers the main call semantics and return nature well, though without an output schema it could more fully explain the typed answer structure and error behavior.

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 defines the parameters in detail and the baseline is 3. The description adds some useful semantics, such as state being text or structured JSON and every question seeing every image, but much of this is already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: asking SubQ's Snap decision model typed questions about a state in a single call. The phrase 'one or more typed questions (choice, score and/or noul)' distinguishes the batch/mixed-question capability from the likely single-type sibling tools such as snap_choice, snap_score, and snap_noul.

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 implied by 'one or more typed questions ... in a single call,' suggesting the tool is for multi-question or mixed-type requests. However, it does not explicitly state when to use snap_decide versus the sibling tools or when not to use it.

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