Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

check_approval_status

Reads authoritative Blender approval-request metadata by request ID without approving, resuming, or consuming authorization, returning token-free state and token_consumed.

Instructions

Read authoritative Blender approval-request metadata without approving, resuming, or consuming authorization. Returns token-free request state and token_consumed; approval or token consumption does not prove successful task execution.

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": {
      "request_id": "<request_id>"
    },
    "name": "check_approval_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesExact Blender approval request ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 must carry the full behavioral burden. It does well on the read-only guarantee and the semantic caveat about approval not implying success, but says nothing about authorization prerequisites, failure modes for an invalid or expired request_id, or rate/consistency behavior of the 'authoritative' read.

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?

Two dense sentences with no filler; the read-only scope is front-loaded and the important caveat about token consumption closes it. Nothing could be removed without losing signal.

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?

For a single-parameter, no-output-schema tool, the description covers what is returned (token-free request state and token_consumed) and warns against a common misreading. Minor gaps remain around error conditions and what fields constitute request state.

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?

Only one parameter and the schema documents it at 100% coverage ('Exact Blender approval request ID'), so the description adds nothing beyond the schema. Baseline 3 applies when the schema does the work.

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 (read authoritative Blender approval-request metadata) and clarifies the negative space (without approving, resuming, or consuming authorization). That negation effectively separates it from approval/resume siblings, though it does not name them directly.

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?

Implies the correct usage context: check request state rather than act on it, and the closing caveat ('approval or token consumption does not prove successful task execution') routes the agent elsewhere for execution status. No explicit 'use this instead of X' phrasing, but the when/when-not boundary is clear.

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