Skip to main content
Glama

register_workspace

Registers an additional named workspace or package in a monorepo or multi-repo evidence bundle, letting agents track each project path under one bundle.

Instructions

Registers an additional named workspace or package within a monorepo or multi-repo evidence bundle.

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": {
      "bundleId": "<bundleId>",
      "name": "<name>",
      "path": "<path>"
    },
    "name": "register_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name for the workspace (e.g. "frontend", "backend", "shared").
pathYesPath to the workspace root directory (absolute or relative to bundle root).
bundleIdYesThe unique identifier of the evidence bundle.
workspacePathNoOptional workspace path hint to locate the bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.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 behavioral burden for a mutating operation. It does not say what happens on a duplicate name (the schema hints names are unique), whether the call is idempotent, whether the caller needs any authorization, or what is returned or mutated in the bundle.

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

Conciseness4/5

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

A single sentence with the key noun phrase front-loaded and no filler. It is efficient, though its brevity is close to under-specification for a write operation with four parameters.

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?

For a mutation tool with no annotations and no output schema, the description leaves significant gaps: precondition that the bundle exists, duplicate-name behavior, effect on existing bundle contents, and any indication of the result. The rich schema covers inputs but not behavior.

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 coverage is 100%, so all four parameters (bundleId, name, path, workspacePath) are already documented in the schema, setting the baseline at 3. The description adds only the notion that the name is a workspace/package label registered within the bundle, and says nothing about how 'path' and 'workspacePath' differ or interact.

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?

Specific verb-plus-resource: 'Registers an additional named workspace or package' with scope 'within a monorepo or multi-repo evidence bundle'. An agent can tell this creates a workspace entry inside an existing bundle rather than a bundle itself. It does not explicitly distinguish itself from siblings like create_evidence_bundle, but the resource noun is distinct enough.

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?

The word 'additional' implies the bundle must already exist and that this is a follow-up to bundle creation, which is useful implied context. However, there is no explicit when-to-use statement, no mention of preconditions or required prior steps, and no named alternative.

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