Skip to main content
Glama

add_module

Create a new module as a reusable code boundary, mapped to a directory, with explicit file assignment and external dependency tracking.

Instructions

Create a new module (reusable code boundary). A module maps to a directory. Files are assigned explicitly via add_file_to_module. Use external_dependencies to record wrapped libraries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesModule name (e.g., 'wallet_connection', 'validation')
pathYesDirectory path relative to source root (e.g., 'src/wallet_connection/')
descriptionNoWhat this module does
purposeNoDomain concern this module owns (one sentence)
external_dependenciesNoLibraries/services this module wraps (e.g., ['walletconnect', 'stripe'])
Behavior2/5

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

Annotations only provide readOnlyHint=false, destructiveHint=false, idempotentHint=false. Description states creation but does not disclose side effects like overwrite behavior, permissions needs, rate limits, or error conditions for existing modules.

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?

Three concise sentences, front-loaded with purpose, efficient use of words.

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?

Lacks return value description and handling of duplicate module names. With 5 parameters and no output schema, more detail on behavior is needed for completeness.

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 description coverage is 100%, each parameter well-described. Description adds context about file assignment and external_dependencies, but value is marginal beyond 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 clearly states the tool creates a new module as a reusable code boundary, distinguishes from sibling add_file_to_module by noting files are assigned explicitly via that tool, and mentions external_dependencies for wrapped libraries.

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?

Provides guidance on module-directory mapping, explicit file assignment via add_file_to_module, and use of external_dependencies. Does not explicitly exclude scenarios, but context is clear compared to siblings.

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/aryanduntley/aimfp'

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