Skip to main content
Glama

ai_modeling_canvas_bind_lab

Attach an Agent Astra/Lab request card to an existing Lab node by its card message ID, not an ordinary chat message.

Instructions

Attach a real Agent Astra/Lab request card to an existing Lab node. Use the card message ID, not an ordinary chat message.

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": {
      "labNodeId": "<labNodeId>",
      "messageId": "<messageId>"
    },
    "name": "ai_modeling_canvas_bind_lab"
  }
}

Input Schema

NameRequiredDescriptionDefault
labNodeIdYes
messageIdYes

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?

The annotations already declare that this is a non-read-only, non-destructive, open-world mutation. The description adds that the target node must already exist and that the message must be a real card, not a chat message, which is useful context beyond the structured fields. It still does not say whether a second bind replaces the existing card, what the operation returns, or how it fails on an invalid message ID.

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?

The description is two short sentences with zero waste. The operation is stated first, and the input constraint that prevents the most likely misuse follows immediately.

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?

There is no output schema, and both parameters are undocumented in the schema, so the description should probably say more about the effect of binding and about failures. What it covers, namely the target node and the source card type, is accurate, but the definition is not complete for a mutation tool with two opaque ID parameters.

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?

With 0% schema description coverage, this dimension depends entirely on the description. The description does clarify that messageId is a card message ID, not an ordinary chat message, and that labNodeId points to an existing Lab node. It gives no format detail for the ID patterns and does not state whether either value is a raw UUID or a prefixed ID, so it only partly compensates.

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 uses a specific verb and resource pair: 'Attach a real Agent Astra/Lab request card to an existing Lab node.' That is concrete enough for an agent to understand the operation. It does not name or differentiate itself from nearby siblings such as ai_modeling_canvas_lab_inputs or ai_modeling_canvas_lab, so it falls short of a 5.

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?

'Use the card message ID, not an ordinary chat message' is a genuine usage constraint on the input, and 'existing Lab node' implies the node must already exist. However, the description gives no guidance on when to choose this tool over sibling operations, and it does not state what to do if the card is already bound. Usage guidance is therefore implied rather than spelled out.

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