Skip to main content
Glama
vuluu2k
by vuluu2k

saveToInbox

Capture thoughts, ideas, or items for later processing by saving them to an inbox within a structured knowledge base.

Instructions

Save a quick thought, idea, or item to the inbox for later processing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe text to capture in the inbox

Implementation Reference

  • The actual business logic implementation of 'saveToInbox' in the Brain class, which handles updating the inbox file or creating it if it doesn't exist.
    async saveToInbox(text: string): Promise<void> {
      const log = getLogger();
    
      try {
        await this.sync.atomicUpdate(
          "inbox",
          (current) => appendInboxItem(current, text),
          `feat(ai): save to inbox`
        );
        log.info("saveToInbox", { text });
      } catch (err) {
        if (isNotFound(err)) {
          const content = appendInboxItem(`# Inbox\n\n`, text);
          await this.sync.createSection(
            "inbox",
            content,
            `feat(ai): create inbox with new item`
          );
          log.info("saveToInbox: created file");
          return;
        }
        throw err;
      }
    }
  • Registration of the 'saveToInbox' tool in the MCP server, which calls the Brain class handler.
    server.registerTool(
      "saveToInbox",
      {
        description:
          "Save a quick thought, idea, or item to the inbox for later processing",
        inputSchema: {
          content: z.string().describe("The text to capture in the inbox"),
        },
      },
      toolHandler("saveToInbox", async ({ content }) => {
        await brain.saveToInbox(content);
        return { success: true };
      })
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as permissions needed, whether it's idempotent, how items are stored or organized in the inbox, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's front-loaded with the core purpose and appropriately sized for the tool's simplicity, making it easy to parse quickly.

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 tool's mutation nature, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'saving' entails (e.g., creates a new item, returns an ID), how the inbox is structured, or error conditions. For a tool with potential complexity in a system with many siblings, this leaves significant gaps.

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?

The description implies a 'content' parameter but doesn't add meaning beyond the schema, which has 100% coverage and fully describes the single parameter. The baseline score of 3 is appropriate since the schema does the heavy lifting, though the description doesn't compensate for any gaps (none exist here).

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 with a specific verb ('Save') and resource ('to the inbox'), and specifies the type of content ('quick thought, idea, or item'). However, it doesn't explicitly differentiate from sibling tools like 'addNote' or 'addTask', which might have overlapping functionality.

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 provides minimal guidance by mentioning 'for later processing', but offers no explicit when-to-use rules, prerequisites, or alternatives. It doesn't clarify when to choose this over similar tools like 'addNote' or 'addTask', leaving usage context vague.

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/vuluu2k/knowledge_mcp'

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