Skip to main content
Glama
AshMet
by AshMet

vibemap_submit_code_map

Submit a structural code map of your codebase to VibeMap. Define nodes for pages, APIs, models, and edges for imports, routes, reads, writes.

Instructions

Submit a structural code map of the user's codebase to VibeMap (rendered on the project's Codebase tab). Build it yourself from your codebase access: one node per meaningful unit (page/route, API endpoint, data model, service, module, config), edges for imports/routes/reads/writes. Node kinds: page|api|model|service|module|config. Layers: ui|api|data|services|shared. Edge kinds: imports|routes|reads|writes. Use repo-relative paths as node ids. Max 500 nodes — aggregate small files into their module. Re-submitting replaces the project's map and resets it to draft for the user to re-confirm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapYes{ nodes: [{id,label,kind,path,layer,summary?}], edges: [{source,target,kind}], stats?: {totalFiles,scannedAt} }
anchorNoOptional sync anchor: { commitSha?, scannedAt? } (git rev-parse HEAD)
projectIdYesVibeMap project to attach the map to
Behavior5/5

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

Annotations indicate a write operation (readOnlyHint=false) but non-destructive. The description adds critical behavioral info: re-submitting replaces the map and resets to draft, max 500 nodes, and aggregation rules.

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?

Front-loaded with purpose; well-structured but slightly long. Every sentence adds value though it could be condensed.

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?

Missing expected output/response behavior (e.g., success indication). No output schema. For a submission tool, the return value or confirmation should be described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but descriptions are minimal. The narrative description greatly enriches parameter meaning: explaining node/edge kinds, ids, layers, and aggregation policy.

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 submits a structural code map, defines what constitutes a map (nodes/edges with constraints), and differentiates from sibling 'vibemap_scan_codebase' by specifying 'Build it yourself'. It also notes that re-submitting replaces the previous map.

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?

The description implicitly tells when to use (when you want to manually provide a map) and contrasts with automated scanning. However, it does not explicitly list alternatives or state when not to use.

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/AshMet/vibemap-mcp'

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