Skip to main content
Glama
LMPrado-DZ23

DZ23 Subagents Universal MCP

by LMPrado-DZ23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Initialize project memory

project_init
Idempotent

Creates or updates shared project metadata with a stable project_id, enabling subsequent tool calls to reference the same project without cloning or reading the repository.

Instructions

Create or update shared project metadata. Does not clone or read the repository. Use one stable project_id per repository and pass it to every later tool call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNoBranch name as recorded by the harness.
workspaceNoWorkspace path as recorded by the harness.
project_idYesProject memory identifier. Not an authorization boundary.
repositoryNoRepository URL or path as recorded by the harness.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / project_id / pattern
      Previous value: -"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"New value: +"^[a-zA-Z0-9](?:[a-zA-Z0-9._-]{0,118}[a-zA-Z0-9_-])?$"
    • changedInput schema / properties / project_id / x-pattern-reason
      Previous value: -"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"New value: +"must use 1-120 letters, digits, dots, underscores or hyphens, start with a letter or digit and not end with a dot"
  2. Changed12 schema fields changedv3.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / branch / description
      Added value: +"Branch name as recorded by the harness."
    • addedInput schema / properties / branch / maxLength
      Added value: +255
    • addedInput schema / properties / project_id / description
      Added value: +"Project memory identifier. Not an authorization boundary."
    • addedInput schema / properties / project_id / maxLength
      Added value: +120
    • addedInput schema / properties / project_id / minLength
      Added value: +1
    • addedInput schema / properties / project_id / pattern
      Added value: +"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"
    • addedInput schema / properties / project_id / x-pattern-reason
      Added value: +"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"
    • addedInput schema / properties / repository / description
      Added value: +"Repository URL or path as recorded by the harness."
    • addedInput schema / properties / repository / maxLength
      Added value: +1024
    • addedInput schema / properties / workspace / description
      Added value: +"Workspace path as recorded by the harness."
    • addedInput schema / properties / workspace / maxLength
      Added value: +1024
  3. First observedv2.2.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context by clarifying that it never clones or reads the repository and that it performs create-or-update semantics. It does not describe auth or persistence details, but the annotations carry the safety profile.

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-load the action and scope, then give the critical ID-stability instruction. There is no filler or redundancy.

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

Completeness4/5

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

For a low-complexity init tool with idempotentHint=true and no output schema, the description covers purpose, boundaries, and the key usage rule. It could be slightly more explicit about update/overwrite behavior, but 'create or update' plus the schema's parameter descriptions make it adequate.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds extra meaning for project_id by requiring one stable ID per repository and reuse across later calls, which is not fully captured in the schema. Other parameters are already well-documented by the schema.

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

Purpose5/5

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

The description uses a specific verb phrase, 'Create or update shared project metadata,' and immediately clarifies what it does not do: 'Does not clone or read the repository.' This clearly identifies the tool's resource and action while distinguishing it from repository-access tools.

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

Usage Guidelines4/5

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

It gives concrete guidance to use one stable project_id per repository and pass it to every later tool call, and it states a key exclusion (does not clone or read the repo). It does not explicitly name alternatives, but the negative boundary plus the ID convention provides sufficient usage context.

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