Skip to main content
Glama

capacities_save_to_daily_note

Save markdown text to today's daily note in a specific Capacities space. Use this tool to organize and store content efficiently within your knowledge management system.

Instructions

Add markdown text to today's daily note in a Capacities space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mdTextYesThe markdown text to add to today's daily note
noTimestampNoIf true, no time stamp will be added to the note
originNoOptional origin label for the content (only 'commandPalette' is supported)
spaceIdYesThe UUID of the space to save to the daily note

Implementation Reference

  • The main handler function that executes the tool: constructs a request body from args, makes a POST API call to /save-to-daily-note, handles the response, and throws errors if failed.
    execute: async (args: {
    	spaceId: string;
    	mdText: string;
    	origin?: "commandPalette";
    	noTimestamp?: boolean;
    }) => {
    	try {
    		const requestBody = {
    			spaceId: args.spaceId,
    			mdText: args.mdText,
    			...(args.origin && { origin: args.origin }),
    			...(args.noTimestamp !== undefined && {
    				noTimestamp: args.noTimestamp,
    			}),
    		};
    
    		const response = await makeApiRequest("/save-to-daily-note", {
    			method: "POST",
    			body: JSON.stringify(requestBody),
    		});
    
    		// Check if response has content before parsing JSON
    		const responseText = await response.text();
    		if (!responseText.trim()) {
    			return "Success: Content saved to daily note (no response data)";
    		}
    
    		try {
    			const data = JSON.parse(responseText);
    			return JSON.stringify(data, null, 2);
    		} catch (parseError) {
    			return `Success: Content saved to daily note. Response: ${responseText}`;
    		}
    	} catch (error) {
    		throw new Error(
    			`Failed to save to daily note: ${error instanceof Error ? error.message : String(error)}`,
    		);
    	}
    },
  • Zod schema defining the input parameters: spaceId (UUID), mdText (string max 200k), optional origin and noTimestamp.
    parameters: z.object({
    	spaceId: z
    		.string()
    		.uuid()
    		.describe("The UUID of the space to save to the daily note"),
    	mdText: z
    		.string()
    		.max(200000)
    		.describe("The markdown text to add to today's daily note"),
    	origin: z
    		.enum(["commandPalette"])
    		.optional()
    		.describe(
    			"Optional origin label for the content (only 'commandPalette' is supported)",
    		),
    	noTimestamp: z
    		.boolean()
    		.optional()
    		.describe("If true, no time stamp will be added to the note"),
    }),
  • src/server.ts:28-28 (registration)
    Registers the saveToDailyNoteTool with the FastMCP server instance.
    server.addTool(saveToDailyNoteTool);
Behavior3/5

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

Annotations indicate readOnlyHint=false (implying a write operation) and openWorldHint=true (suggesting flexible use), which the description aligns with by describing an 'Add' action. However, it doesn't add significant behavioral context beyond annotations, such as whether the text is appended or overwritten, or any rate limits or permissions needed.

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 core action and resource without unnecessary details. It's appropriately sized for the tool's complexity, with zero waste or redundancy.

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?

Given the tool's moderate complexity (4 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral nuances, or output expectations, leaving gaps that could hinder an AI agent's effective use.

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?

With 100% schema description coverage, the input schema fully documents all parameters, including mdText, noTimestamp, origin, and spaceId. The description mentions 'markdown text' and 'today's daily note', which loosely maps to mdText and implies a date context, but adds minimal semantic value beyond the schema.

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 action ('Add markdown text') and target resource ('today's daily note in a Capacities space'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like capacities_save_weblink, which might also involve saving content but to different resources.

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 no guidance on when to use this tool versus alternatives, such as capacities_save_weblink for saving links or capacities_search for finding notes. It lacks context on prerequisites (e.g., needing a valid spaceId) or exclusions, leaving usage 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

Related 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/jem-computer/capacities-mcp'

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