Skip to main content
Glama

static.md

by md.static
OverviewDiscussionsAdmin

Create a note

create_note

Creates a markdown note owned by the signed-in user, optionally in a folder, and returns its link. New notes open to anyone with the link, like notes made on static.md; the owner can restrict them in static.md.

Input Schema

NameRequiredDescriptionDefault
titleNoShort title (static.md keeps the first 32 characters)
folderNoFolder to put the note in, such as "work/launch"; it is made if it doesn't exist yet. A folder the user already has can be given exactly as the list tools show it, spaces included. Default: the top level ("/")
markdownNoInitial markdown content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / folder / description
      Previous value: -"Folder to put the note in, such as \"work/launch\"; it is made if it doesn't exist yet. Default: the top level (\"/\")"New value: +"Folder to put the note in, such as \"work/launch\"; it is made if it doesn't exist yet. A folder the user already has can be given exactly as the list tools show it, spaces included. Default: the top level (\"/\")"
  2. Changed1 schema field changed
    • addedInput schema / properties / folder
      Added value: +{
+  "description": "Folder to put the note in, such as \"work/launch\"; it is made if it doesn't exist yet. Default: the top level (\"/\")",
+  "maxLength": 700,
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the mutation profile (non-read-only, non-idempotent, non-destructive); the description adds genuinely non-obvious behavior — that new notes are link-readable by anyone by default — plus how access is later restricted. That is exactly the kind of consequence an agent could not infer from structured fields. It doesn't cover title truncation effects or authorization requirements, keeping it below 5.

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?

Two sentences, front-loaded with the core action and its outcome, and the security-relevant default appears immediately after. Slightly compressed by the shared link/site reference, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, no-output-schema creation tool this covers action, ownership, optional organizational context, return value, and the privacy default. Missing failure behavior (invalid or overly long folder, exceeding 200k markdown) is minor given full schema documentation.

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?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by framing folder as optional and confirming a link is returned, but it adds no syntax or format detail beyond what the schema already documents (max lengths, default '/', folder auto-creation, 32-character title retention).

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?

States a specific verb and resource (creates a markdown note), ownership (signed-in user), optional placement (folder), and return value (link). It implicitly distinguishes itself from create_note_ciphertext by specifying markdown, but never names that sibling, so the differentiation is inferred rather than explicit.

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

Usage Guidelines3/5

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

Provides context (notes behave like static.md notes) but no explicit when-to-use or when-not-to-use guidance, and no steering toward create_note_ciphertext for encrypted content or create_board for other artifacts. Usage is only implied by the word 'markdown'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All static.md toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources