Skip to main content
Glama

ai_modeling_canvas_events

Read-only

Read real-time events from an Agent turn or 3D Lab job with bounded polling and a resume cursor for incremental updates. Does not start tasks.

Instructions

Read bounded real-time Agent or 3D Lab events, returning a resume cursor. Does not start a task.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "ai_modeling_canvas_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAgent turn ID or Lab job ID.
kindYes
after_idNoResume strictly after this event ID.
max_eventsNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds two real behavioral facts: results are bounded and a resume cursor is returned, which implies resumable incremental reads. It does not disclose that wait_seconds makes the call block/long-poll for up to 50 seconds, nor what event types come back.

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 short sentences, front-loaded with the action and resource, with the exclusion clause last. Nothing is redundant or padded.

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 5-parameter read tool with no output schema, the description covers purpose and the cursor return shape. It leaves gaps on the kind enum's meaning (agent turn vs lab job), the blocking behavior of wait_seconds, and the practical polling pattern an agent would need to use it well.

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 only 40%, so kind, id, and after_id are documented in the schema while max_events and wait_seconds are not. The description's 'bounded' and 'resume cursor' phrases loosely map to max_events and after_id but add no detail, and the blocking semantics of wait_seconds (default 20, max 50) remain undocumented in both places.

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?

The description names a specific verb ('Read') and resource ('real-time Agent or 3D Lab events') and scopes it as 'bounded'. The closing clause 'Does not start a task' carves out a clear boundary against task-starting siblings such as ai_modeling_canvas_run or _continue, though no sibling is named explicitly.

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?

There is one useful negative guideline ('Does not start a task'), which tells the agent this is observation-only. However, it gives no positive when-to-use guidance, no mention of when to prefer a job-status sibling like ai_modeling_canvas_lab_job_get, and no polling-vs-blocking advice.

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