SomaCheck Vibecheck

Vibecheck Status

get_vibecheck_status

Read-onlyIdempotent

Read the SomaCheck database feed before posting. Reports available proposition capacity, when routine replenishment is due, and whether this is the agent's first contact. Database state does not verify phone display.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`linked`	Yes
`cadence`	Yes
`first_run_intro`	Yes
`no_prior_requests`	Yes
`recommended_action`	Yes
`has_pending_request`	Yes
`prior_request_count`	Yes
`propositions_needed`	Yes
`queued_proposition_count`	Yes
`pending_proposition_count`	Yes
`replenishment_requested_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

removedOutput schema / properties / copy_guidance

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "fallback": {
-      "type": "string"
-    },
-    "framing": {
-      "type": "string"
-    },
-    "policy": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "policy",
-    "framing",
-    "fallback"
-  ],
-  "type": "object"
-}

changedOutput schema / required

Previous value: -[
-  "linked",
-  "no_prior_requests",
-  "prior_request_count",
-  "has_pending_request",
-  "pending_proposition_count",
-  "queued_proposition_count",
-  "propositions_needed",
-  "replenishment_requested_at",
-  "first_run_intro",
-  "cadence",
-  "recommended_action",
-  "copy_guidance"
-]New value: +[
+  "linked",
+  "no_prior_requests",
+  "prior_request_count",
+  "has_pending_request",
+  "pending_proposition_count",
+  "queued_proposition_count",
+  "propositions_needed",
+  "replenishment_requested_at",
+  "first_run_intro",
+  "cadence",
+  "recommended_action"
+]

First observedSep 12, 2026

TDQS

A4.8/5.0

Behavior4/5

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

The description adds value beyond the annotations by explaining that the tool reports a specific set of data points (capacity, replenishment due, first contact) and caveats that the database state does not verify phone display. Since annotations already declare readOnly, idempotent, and non-destructive hints, the description enriches the behavior by clarifying the scope and limitations.

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 three sentences long, each earning its place: the first states the usage context and purpose, the second lists the reported items, and the third clarifies a limitation. It is front-loaded with the key action ('Read... before posting') and succinctly covers necessary nuances without redundancy.

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?

The description is fully complete for a zero-parameter tool with a rich output schema and annotations. It explains what the tool does, what it reports, and its limitations. Nothing an agent needs to decide whether to invoke it is missing; the output schema handles return values.

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?

The tool has zero parameters, so the description carries the full burden of explaining what the tool provides. It details the meaning of the output, which is valuable given the output schema exists but the description adds context about the kind of status information offered. With no parameters, the description is complete in this dimension.

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 clearly states the tool reads a specific database feed (SomaCheck) and reports on three distinct aspects: available capacity, replenishment timing, and first-contact status. It distinguishes itself from siblings by focusing on the status of the database feed before posting, versus context, results, posting, or requesting.

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

Usage Guidelines5/5

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

The description explicitly instructs to use this tool before posting, indicating it is a preparatory read for other actions. It contrasts with the purpose of verifying phone display, implying it's not for display verification, and the sibling names suggest alternatives for context and posting. This clearly guides an agent on when to use this tool.

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?