Skip to main content
Glama
Sign In
@vibemap.ai/mcp-server

@vibemap.ai/mcp-server

by AshMet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibemap_unblock_criterion

Reverses a blocked criterion to its previous status by recording how the blocker was resolved.

Instructions

Unblock a criterion. Transitions blocked → prior_status (recorded when block was set; defaults to ready).

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": {
      "criterionId": "<criterionId>",
      "resolution": "<resolution>"
    },
    "name": "vibemap_unblock_criterion"
  }
}

Input Schema

NameRequiredDescriptionDefault
resolutionYesHow the blocker was resolved (1-2000 chars)
criterionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations provide minimal safety info (not read-only, not destructive, not idempotent). The description adds the state transition behavior, but lacks details on error conditions or prerequisites like the criterion needing to be blocked.

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?

Single sentence that is front-loaded with the core action and immediately explains the state transition. No wasted words.

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

Completeness3/5

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

For a simple mutation tool without an output schema, the description covers the essential state change. However, it does not mention return value, error scenarios (e.g., criterion not found or not blocked), or prerequisites.

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

Parameters2/5

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

Schema coverage is 50% (only 'resolution' has a description). The tool description does not add any parameter-level detail beyond what the schema provides. 'criterionId' remains undocumented.

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 verb 'Unblock' and the resource 'criterion', and explains the state transition from 'blocked' to 'prior_status'. This distinguishes it from the sibling tool 'vibemap_block_criterion'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., when a criterion should be unblocked). The description relies on the tool name to imply usage.

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

Deploy Server

Other Tools