Skip to main content
Glama

Snap: score question

snap_score

Rates a state on a custom ordered 2–10 level scale and returns a probability-weighted score, level legend, per-level probabilities, and confidence for triage, risk scoring, or routing decisions.

Instructions

Ask SubQ's Snap decision model a single Score question: rate a state on an ordered scale of 2-10 levels you define. Returns a probability-weighted score (it can fall between levels), the level legend, per-level probabilities, and a confidence value, 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>",
      "levels": "<levels>"
    },
    "name": "snap_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOptional Snap model id override (default: subq-snap-1.2).
stateYesThe situation to rate: 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.
levelsYesOrdered level descriptions, lowest to highest (2-10). Each level may be a string or a structured entry.
instructionsYesWhat Snap should rate: 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. Changed5 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 / levels / items / 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"
      +  }
      +]
    • 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

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses that the returned score is probability-weighted and can land between levels, plus the level legend, per-level probabilities, confidence, and the 'answer' key. It omits nothing critical for a read-only inference call, though it says nothing about latency, cost, or failure modes.

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?

A compact, front-loaded sentence that states what to ask, what the scale is, and what comes back, with no filler. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters with three required and no output schema, yet the description compensates by describing the return payload in detail, which is exactly the gap an absent output schema leaves. The 'single Score question' phrasing also clarifies the batch-versus-single ambiguity raised by the shared-images schema note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter is documented, including the role of 'instructions', the 'state' variants and the 2-10 level range. The description's 'levels you define' wording reinforces those semantics without conflicting with the schema, though it does not add new detail beyond it, so this is a solid but not exceptional case.

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?

States a specific verb and resource: ask Snap a single Score question that rates a state on an ordered 2-10 level scale. The 'ordered scale' framing implicitly separates it from choice-style siblings, though it never names snap_choice or snap_decide to make the routing 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 is implied by the scale-rating framing, but there is no explicit when-to-use versus when-not guidance, no mention of alternatives among snap_choice/snap_decide, and no prerequisites or limits stated. An agent must infer the selection rule from the scale semantics alone.

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