Skip to main content
Glama
camiloluvino

Roam Research MCP Server

by camiloluvino

roam_markdown_cheatsheet

Access Roam Research's markdown formatting guide to learn syntax for creating and editing content in your knowledge graph.

Instructions

Provides the content of the Roam Markdown Cheatsheet resource, optionally concatenated with custom instructions if CUSTOM_INSTRUCTIONS_PATH is set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that loads, caches, and returns the Roam Markdown Cheatsheet content, optionally appending custom instructions from an environment-specified path.
    async getRoamMarkdownCheatsheet() {
      if (this.cachedCheatsheet) {
        return this.cachedCheatsheet;
      }
    
      const __filename = fileURLToPath(import.meta.url);
      const __dirname = path.dirname(__filename);
      const cheatsheetPath = path.join(__dirname, '../../Roam_Markdown_Cheatsheet.md');
    
      try {
        let cheatsheetContent = await fs.promises.readFile(cheatsheetPath, 'utf-8');
    
        const customInstructionsPath = process.env.CUSTOM_INSTRUCTIONS_PATH;
        if (customInstructionsPath) {
          try {
            // Check if file exists asynchronously
            await fs.promises.access(customInstructionsPath);
            const customInstructionsContent = await fs.promises.readFile(customInstructionsPath, 'utf-8');
            cheatsheetContent += `\n\n${customInstructionsContent}`;
          } catch (error) {
            // File doesn't exist or is not readable, ignore custom instructions
            if ((error as NodeJS.ErrnoException).code !== 'ENOENT') {
              console.warn(`Could not read custom instructions file at ${customInstructionsPath}: ${error}`);
            }
          }
        }
    
        this.cachedCheatsheet = cheatsheetContent;
        return cheatsheetContent;
      } catch (error) {
        throw new Error(`Failed to read cheatsheet: ${error}`);
      }
    }
  • The schema definition for the 'roam_markdown_cheatsheet' tool, including name, description, and empty input schema (no parameters required).
    [toolName(BASE_TOOL_NAMES.MARKDOWN_CHEATSHEET)]: {
      name: toolName(BASE_TOOL_NAMES.MARKDOWN_CHEATSHEET),
      description: 'Provides the content of the Roam Markdown Cheatsheet resource, optionally concatenated with custom instructions if CUSTOM_INSTRUCTIONS_PATH is set.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • The registration and dispatching logic in the MCP server request handler that routes calls to 'roam_markdown_cheatsheet' to the corresponding tool handler method.
    case BASE_TOOL_NAMES.MARKDOWN_CHEATSHEET: {
      const content = await this.toolHandlers.getRoamMarkdownCheatsheet();
      return {
        content: [{ type: 'text', text: content }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the tool as providing content and optionally concatenating with custom instructions, but it lacks details on critical behaviors: for example, whether this is a read-only operation, if it requires authentication, what the output format is (e.g., plain text, structured data), or any rate limits. The description is minimal and does not compensate for the absence of annotations.

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 a single, efficient sentence that front-loads the main purpose ('Provides the content of the Roam Markdown Cheatsheet resource') and adds a conditional detail without unnecessary elaboration. Every word earns its place, making it appropriately sized and well-structured for clarity.

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?

Given the context: no annotations, no output schema, and 0 parameters, the description is incomplete. It explains what the tool does but lacks essential details for an AI agent, such as the return type (e.g., markdown text, error handling), behavioral traits (e.g., read-only, side effects), or how it integrates with sibling tools. The description does not compensate for the missing structured information, making it inadequate for full understanding.

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?

The input schema has 0 parameters with 100% coverage, so no parameters are documented in the schema. The description mentions an optional 'CUSTOM_INSTRUCTIONS_PATH' parameter, adding semantic meaning beyond the schema by indicating that custom instructions can be concatenated if this path is set. This provides useful context for potential parameter usage, though it's not a formal parameter in the schema. Since there are 0 parameters, the baseline is 4, and the description adds value by hinting at optional behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: it provides content from a specific resource (the Roam Markdown Cheatsheet). It specifies the verb 'provides' and the resource 'Roam Markdown Cheatsheet', making the action and target explicit. However, it does not distinguish this from sibling tools like 'roam_import_markdown' or 'roam_search_by_text', which might also involve markdown or content retrieval, so it lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes no guidance on when to use this tool versus alternatives. It mentions an optional feature (concatenation with custom instructions) but does not explain scenarios where this tool is preferred over other content-fetching or markdown-related siblings, such as 'roam_fetch_page_by_title' or 'roam_import_markdown'. There is no explicit when/when-not or alternative tool references, leaving usage context unclear.

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/camiloluvino/roamMCP'

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