Skip to main content
Glama

session_status

Inspect a remote Blender session's worker, checkpoint, and recent jobs, and refresh user activity to monitor status and troubleshoot issues.

Instructions

Inspect remote worker, checkpoint and recent jobs; refresh user activity.

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": {
      "session_id": "<session_id>"
    },
    "name": "session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. The phrase "refresh user activity" implies a side effect (a keep-alive or activity-timestamp write) but never says whether it mutates state, requires permissions, or is optional; the inspection scope (worker, checkpoint, jobs) is also left unqualified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, which is good, but the brevity comes at the cost of vagueness rather than being tightly packed with useful information. The semicolon splice merges two unrelated concerns (inspection vs. activity refresh) without structure.

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

Completeness2/5

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

With no annotations, no output schema, and 0% parameter coverage, the description should explain what the returned status contains and what the required session_id is. It does neither, leaving an agent able to guess only that it inspects something session-related.

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 description coverage is 0% and there is one required parameter, session_id, which the description never mentions. With no guidance on where the identifier comes from (create_session or list_sessions) or whether it accepts a name or id, the description adds nothing beyond the bare property name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Inspect remote worker, checkpoint and recent jobs" lists resources an agent would not expect from a tool named session_status, and it never says what a session status actually is. With siblings job_status and list_checkpoints present, the definition gives no basis for telling this tool apart from them.

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?

There is no indication of when to call this versus job_status, list_checkpoints, list_sessions, or get_logs. No preconditions, no exclusions, no alternatives are named.

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