Skip to main content
Glama
Im-Hal-9K

Capacities-MCP-Plus

capacities_save_to_daily_note

Add markdown text to today's daily note in Capacities for knowledge management and organization.

Instructions

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

Input Schema

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

Implementation Reference

  • The execute function implementing the core logic of the 'capacities_save_to_daily_note' tool. It constructs a request body from input args and sends a POST request to the '/save-to-daily-note' API endpoint using makeApiRequest, then handles the response appropriately.
    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 for the tool: spaceId (UUID string), mdText (max 200k string), optional origin (enum), optional noTimestamp (boolean).
    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:31-31 (registration)
    Registers the saveToDailyNoteTool object (containing name 'capacities_save_to_daily_note', handler, and schema) with the FastMCP server instance.
    server.addTool(saveToDailyNoteTool);
Behavior3/5

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

Annotations provide readOnlyHint=false (indicating mutation) and openWorldHint=true (suggesting flexible use), but the description adds minimal behavioral context. It mentions adding text to a daily note but doesn't disclose whether this appends or overwrites, how content is formatted, or any rate limits. With annotations covering basic safety, the description adds some value but lacks operational details.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a mutation tool with 4 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It clarifies the target is a daily note, but lacks details on behavior (e.g., append vs. overwrite), error handling, or integration with sibling tools. The annotations help, but more context would improve completeness.

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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description doesn't add any meaning beyond what the schema provides—it mentions 'markdown text' and 'today's daily note' but these are already covered by mdText and implied by the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

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 understandable. It doesn't explicitly differentiate from sibling tools like capacities_save_weblink, which would require mentioning this is specifically for daily notes rather than general saving operations.

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 like capacities_save_weblink or capacities_search. It mentions the target is 'today's daily note' but doesn't explain when daily notes are appropriate versus other content types, nor does it mention prerequisites or constraints beyond what's in the schema.

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/Im-Hal-9K/Capacities-MCP-Plus'

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