SomaCheck Vibecheck

Get Vibecheck Result

get_vibecheck_result

Read-onlyIdempotent

Read one exact proposition or immediate vibecheck by request_id. This is a single non-blocking read: queued is cached, and pending is not answered. Immediate vibecheck handles begin with live: and remain bound to the originating client. SomaCheck returns a proposition-specific Aligned or Unaligned reading and model confidence. Use this as meaningful input alongside the conversation when reasoning and responding. Confidence describes the classifier’s uncertainty.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request_id`	Yes	The opaque request_id returned by post_vibecheck_statement or request_vibecheck.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`verdict`	Yes
`latency_s`	Yes
`confidence`	Yes
`error_code`	No
`expires_at`	No
`request_id`	Yes
`user_feedback`	No
`delivery_state`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedOutput schema / properties / expires_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedSep 14, 2026

addedOutput schema / properties / delivery_state

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "queued",
+        "processing",
+        "sent",
+        "failed",
+        "skipped"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / error_code

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "delivery_timeout",
+        "delivery_failed",
+        "delivery_skipped",
+        "delivery_unavailable",
+        "response_timeout"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveHint, so the safety profile is covered. The description adds substantial behavioral context: 'single non-blocking read', queued vs. pending behavior, 'immediate vibecheck handles begin with live: and remain bound to the originating client', and the meaning of confidence. This goes well beyond the annotations and helps the agent anticipate system behavior.

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?

The description is six sentences long, but each sentence carries distinct information: purpose, non-blocking behavior, live: semantics, output meaning, usage context, and confidence definition. It is front-loaded with the core purpose and avoids redundancy, though it could be slightly tightened by merging the last two sentences.

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?

For a one-parameter tool with a full input schema and an output schema present, the description is very complete. It explains the expected behavior for different request states, the nature of immediate vibechecks, the output semantics (Aligned/Unaligned and confidence), and how to use the result. Nothing essential is missing for correct invocation and interpretation.

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

Parameters4/5

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

Schema coverage is 100% because request_id has a description, providing the baseline of 3. The description adds extra semantic value by noting that 'immediate vibecheck handles begin with live:' and by distinguishing queued vs. pending states, which give the agent a practical hint about what kind of request_id may be encountered and how the result behaves.

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 clearly states the verb 'Read' and the resource 'one exact proposition or immediate vibecheck by request_id', which is specific. It implicitly distinguishes from siblings like get_vibecheck_status and get_vibecheck_context by focusing on a single result, but it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: 'Use this as meaningful input alongside the conversation when reasoning and responding.' It also explains behavioral conditions, such as 'queued is cached, and pending is not answered,' which informs when results are available. However, it doesn't explicitly exclude alternatives or name sibling tools for different scenarios.

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

All SomaCheck Vibecheck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?