Skip to main content
Glama
theSharque
by theSharque

Set Module Details

set-module-details

Creates or updates a module with its files, dependencies, and data flow. Attach up to 50 entries (APIs, entities) per call to populate slices.

Instructions

Creates or updates one vertical module (files, dependencies, dataFlow sync). IMPORTANT: Slices (api, domain, persistence) are built from entries, not from module text. When adding or updating a module, also add entries this module owns: pass facts[] (http-endpoint, entity, glossary, …) in this call (max 50 per call), or call set-entry / set-entries in 50-entry batches with refs.moduleName=. Max 50 entries per bulk call—split large catalogs into batches of ~50 to avoid oversized tool payloads. For full re-import: delete-entries once, then set-entries in 50-entry chunks; or replace-entries with deleteOrphans=false until the final batch (deleteOrphans=true). Without entries, get-slice will be empty for this module. After edits call validate to verify links. Does not replace other modules. Prefer over set-project-architecture for single-module edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject ID (defaults to normalized workdir)
nameYesModule name
descriptionYesDetailed description of the module
inputsYesWhat the module accepts as input
outputsYesWhat the module produces as output
dependenciesNoList of module dependencies
filesNoFiles belonging to this module; add matching entry kinds per Controller/Repository
factsNoHorizontal facts for this module (APIs, entities, terms). Max 50 per call; use set-entries for more. Each becomes an entry with refs.moduleName set automatically.
usageExamplesNoUsage examples for this module
notesNoAdditional notes or comments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleIdYes
messageYes
entriesCreatedNo
entriesUpdatedNo
entryIdsNo
reminderNo
suggestedKindsNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the max 50 facts per call, automatic setting of refs.moduleName, and the emptiness of get-slice without entries. Could be more explicit about overwrite vs merge behavior on updates.

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?

Single paragraph with clear front-loading of core purpose, followed by important constraints and alternatives. Uses caps for emphasis. Slightly dense but efficient.

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?

Given 10 parameters, high schema coverage, and presence of output schema, the description covers the essential use cases, batching, and relationships. Lacks details on projectId defaulting and exact update semantics, but overall sufficient.

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 coverage is 100%, baseline 3. The description adds meaning beyond schema: explains the relationship between facts and entries, the 50-item limit, and that refs.moduleName is set automatically. Provides usage context for 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 starts with a clear verb and resource: 'Creates or updates one vertical module.' It distinguishes from siblings by noting 'Prefer over set-project-architecture for single-module edits.' Also explains what slices are built from, showing specific scope.

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?

Explicitly states when to use this tool vs alternatives like set-entries. Provides batch splitting guidance, re-import strategy using delete-entries and replace-entries, and warns about the consequences of missing entries. This is comprehensive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theSharque/mcp-architect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server