Skip to main content
Glama

scan

Idempotent

Discover unregistered misterdev projects in a directory and add them to the registry. Use before status, build, or run commands on new projects.

Instructions

Discover misterdev projects under a directory and add them to the registry.

Use when: you have projects on disk that misterdev does not know about yet,
before calling ``status``, ``build``, or ``run`` on them. Do NOT use when:
the projects are already registered (call ``list_projects`` to check) — a
re-scan is harmless but redundant. Related: ``list_projects`` (see what is
registered), ``status`` (inspect a registered project).

Side effects: writes only to misterdev's project registry — it never reads,
edits, or executes any project code, and re-scanning the same directory is
idempotent (no duplicates).

Returns a short confirmation string naming the directory scanned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYesAbsolute path to an existing, readable directory to search recursively for misterdev projects (directories containing a project.yaml). Must be a directory, not a file. Example: '/Users/me/code'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description details side effects: writes only to the registry, never reads/edits/executes code, and is idempotent. Annotations already provide idempotentHint=true and destructiveHint=false, and the description adds specificity and reassurance, with no contradiction.

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?

The description is well-structured with three short paragraphs: purpose, usage guidelines, and side effects/return. It is front-loaded and every sentence adds value, no fluff.

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 simplicity (1 param, output schema exists), the description covers purpose, usage, side effects, and return value. It also references siblings and provides enough context for an agent to decide when to invoke.

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% for the single parameter. The description adds value by mentioning recursive search and the condition 'directories containing a project.yaml', which are not in the schema. Baseline is 3, and this extra context justifies a 4.

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 discovers and registers misterdev projects under a directory. It distinguishes itself from siblings by mentioning 'list_projects' and 'status' as related but different tools, providing a specific verb and resource.

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?

The description explicitly provides when to use (before status/build/run) and when not to use (projects already registered, with reference to list_projects), and gives related alternatives. This is comprehensive guidance.

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/dcondrey/misterdev'

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