Skip to main content
Glama

register_project

Register a project to link it with the CtxNest knowledge system, automatically indexing markdown files and registering declared tools.

Instructions

Register a new project and link it to the CtxNest knowledge system.

SIDE EFFECTS: Writes project metadata to disk (persisted in the CtxNest data directory). Scans the project root recursively to discover and index all markdown files into the local database. Registers any ctxnest.json-declared Hands tools found in the project root. This operation is idempotent — re-registering an existing project updates its metadata without data loss.

AUTH / RATE LIMITS: None. Operates entirely on the local file system.

PARAMETERS:

  • name: Human-readable project name.

  • path: Absolute path to the project root. Required. If the user does not specify, use the current working directory. Fails with a descriptive error if the path does not exist or is inaccessible.

  • description: Optional free-text description stored with the project metadata.

RETURNS: A JSON object containing:

  • project: { id, name, path, description, created_at }

  • discovered_files_count: number of markdown files indexed

  • discovered_files: array of { path, est_tokens, size_bytes } for each file

  • total_est_tokens: estimated total token cost of all discovered files

  • hands: { found, tools_registered, tools_disabled, warnings }

  • warnings: array of non-fatal issues (e.g. scan failures, token budget exceeded)

ERROR CONDITIONS: Returns isError=true if path is missing or unresolvable. Scan failures are non-fatal and reported in warnings rather than as errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
pathNoAbsolute path to the project root. If not provided by the user, use the current working directory.
descriptionNoOptional project description
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: side effects (writes metadata, scans files, idempotent), auth/rate limits (none), error conditions (isError on missing path), and non-fatal warnings. This comprehensive disclosure meets the burden of transparency.

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?

The description is relatively long but well-structured with clear sections (SIDE EFFECTS, AUTH/RATE LIMITS, PARAMETERS, RETURNS, ERROR CONDITIONS). It is front-loaded with the main purpose. While every sentence is informative, some redundancy exists (e.g., repeating parameters from schema), but overall it is efficiently organized for an agent.

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

Completeness5/5

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

Given the tool's complexity (registration, scanning, indexing), the absence of annotations and output schema, this description is remarkably complete. It covers all essential aspects: purpose, side effects, parameter details, return structure, error handling, and even non-fatal warnings. An agent can reliably invoke this tool based solely on the description.

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%, so baseline is 3. However, the description adds significant value: it clarifies that 'path' defaults to the current working directory if not provided, and that it fails with a descriptive error if the path doesn't exist. Additionally, it describes the return object structure in detail, which the schema does not cover (no output schema). This goes beyond mere schema repetition.

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 action 'Register a new project and link it to the CtxNest knowledge system'. It uses a specific verb ('register') and identifies the resource ('project'). The description sufficiently distinguishes this tool from siblings like 'list_projects' or 'refresh_index' by focusing on the registration and initial indexing process.

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?

While the description explains what the tool does and its side effects, it does not explicitly state when to use this tool versus alternatives. For instance, it could mention that 'refresh_index' is for re-indexing after changes, or that 'list_projects' only lists existing projects. The context is clear enough for an agent to infer usage, but explicit guidance is missing.

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/safiyu/ctxnest'

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