Skip to main content
Glama
Sign In
codelattice

codelattice

by aiulms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

codelattice_workspace

Read-onlyIdempotent

Analyze workspace and monorepo structure to map project boundaries, dependency graphs, and cross-project impact. Identify affected areas before making changes.

Instructions

Workspace/monorepo analysis for project boundaries, dependency graph, cross-project impact, overview, or engine-backed job mode. Use this on workspace roots; use codelattice_project only after selecting a manifest-backed project root.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "codelattice_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoAnalysis mode. inspect = workspace inventory (codelattice.workspaceInspection.v1, same envelope as CLI inspect, milliseconds). Use job for large workspaces, then job_status/job_detail with jobId.graph
pageNojob_detail page index
rootNoAbsolute path to workspace root. Required except for job_status/job_detail.
jobIdNoRequired for job_status and job_detail; root is not required for these modes
targetNoTarget for impact mode
compactNo
maxDepthNo
pageSizeNojob_detail page size
directionNoboth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the notion of engine-backed job mode and does not disclose behavior such as job lifecycle, response shape, or how modes like job_cancel relate to the read-only annotation.

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 sentences, front-loaded with the tool's purpose and followed by the single most important usage caveat. No filler or repetition of schema details.

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?

The description plus schema cover the main modes, but there is no output schema and no explanation of what the 'full' mode returns or how target/impact mode works. For a 9-parameter multi-mode tool, the description is useful but not fully complete.

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 67% and the description adds high-level mode guidance, but it does not explain parameters like root, target, compact, maxDepth, or direction beyond what the schema already says. It is adequate but does not compensate for the remaining undocumented 33% of parameters.

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 identifies a specific resource (workspace/monorepo roots) and a concrete task (analysis for boundaries, dependency graph, cross-project impact, overview, or engine-backed job mode). It distinguishes itself from codelattice_project by instructing to use that tool only after selecting a manifest-backed project root.

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

Usage Guidelines5/5

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

'Use this on workspace roots; use codelattice_project only after selecting a manifest-backed project root' is an explicit routing rule with a condition and an alternative. It also signals large-workspace handling through the engine-backed job mode.

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