Skip to main content
Glama

studio_library

Read-only

Browse and query a project's files, requirements, and versions to retrieve versioned robotics development context.

Instructions

studio library

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.1

TDQS

D1.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered without the description. The description adds nothing further: no indication of what the library contains, whether results are paginated, scoped by project, or filtered by section, which the schema alone cannot convey.

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 represent under-specification rather than compression; nothing is front-loaded because nothing is stated. There is no structure to guide a caller.

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?

A read-only listing tool with a nested ten-property arguments object, an idempotency key, an enum-typed section selector, and no output schema demands explanation that the description entirely omits. The definition is not usable without trial-and-error schema inspection.

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 nested arguments object exposes ten undocumented properties (section enum of files/requirements/versions, path, query, limit, basis, intent, state_id, component_id, after). The description offers no meaning for any of them, leaving the caller to infer semantics purely from property names.

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?

"studio library" merely restates the tool name; there is no verb and no statement of what the tool returns or does. An agent cannot distinguish it from siblings like studio_context, studio_overview, or list_artifact_files based on this text.

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?

No when-to-use guidance, no exclusions, and no mention of any alternative among the many studio_* and list_* siblings. The caller has to guess entirely from the schema which tool applies.

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