Skip to main content
Glama

studio_related

Read-only

Retrieves items related to a specified anchor—such as a project, component, file, requirement, CAD, or code—within a versioned robotics development state, with pagination support.

Instructions

studio related

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": {
      "arguments": "<arguments>"
    },
    "name": "studio_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.1

TDQS

D1.1/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not required to restate safety, but it must add something. It adds nothing — no indication of what is fetched, whether results are paginated, or how the anchor/basis affect the read.

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

Conciseness2/5

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

Two words are technically concise, but the problem is under-specification rather than verbosity. There is no structure or front-loaded information because there is no information.

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

Completeness1/5

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

For a tool with a required nested anchor object, a project/state scoping pair, cursor pagination (after/limit), and no output schema, the definition is wholly inadequate. An agent cannot call this correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description compensates for none of it. The nested anchor object with its kind enum (work, project, component, file, cad, code, requirement), plus project_id, state_id, limit, after, basis, and intent, are left entirely unexplained.

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

Purpose1/5

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

"studio related" merely restates fragments of the tool name and states no verb, resource, or outcome. An agent cannot tell what this tool returns or how it differs from studio_context, studio_work, or related_review_context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no preconditions, and no reference to any alternative tool. The agent has nothing to route on beyond the name.

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