Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

get_task_status

Reads the stored status and sanitized outcome of an Agent Manager task by task ID, including approval-binding verification state for tasks awaiting approval.

Instructions

Read the stored status and sanitized outcome of an Agent Manager task in a session. For tasks awaiting approval, reports the local approval binding as unverified (or expired from its recorded deadline); it does not claim Blender still has a pending request.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesUnique Agent Manager task identifier.
session_idNoSession that owns the task.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does it well: it discloses that the data is stored rather than live, that outcomes are sanitized, and that an approval binding may be unverified or expired. It explicitly disclaims claiming Blender still has a pending request, which prevents a costly misinterpretation. It stops short of stating permissions, error conditions, or whether reads mutate any state.

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?

Two tight sentences with the core purpose front-loaded and the approval caveat second. Nothing is wasted, though the second sentence is dense enough to require a second read.

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?

It is a simple two-parameter read with a complete schema, but with no output schema the description should say more about what the returned status and 'sanitized outcome' contain, since the agent cannot infer the shape or value set of the response.

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?

Schema description coverage is 100%, so task_id and session_id (with its 'default' default) are already fully documented. The description adds no per-parameter meaning beyond the schema, which is acceptable at this coverage level but earns only the baseline.

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: reads the stored status and sanitized outcome of an Agent Manager task scoped to a session. It is reasonably distinguishable from generic object/scene tools, but it never contrasts with the sibling check_approval_status, leaving a plausible overlap unresolved.

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 phrase 'stored ... in a session' and the caveat about awaiting-approval tasks, but there is no explicit when-to-use statement, no prerequisites (e.g., task must already exist), and no named alternative such as check_approval_status for live approval queries.

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