Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

notes-create

Destructive

Create a note in the connected user's personal Hjarni account, an authorized shared folder, or a team workspace they belong to. The server enforces write access. Approaching or reaching a note quota may email an account-limit notification to the account or team owner; sent emails cannot be recalled. Required: title (string). Always include a 2-3 sentence summary too (required by convention, even though the schema only enforces title) so the note is useful to future LLM sessions. Optional: body (Markdown with [[id:Note Title]] wiki-links), summary, source_url, container_id, tag_list (comma-separated), team_id (to create in a team), review_after (ISO 8601 datetime, only set this for time-boxed notes that should flag themselves stale after a date). A new note starts verified (status 'active'). Search for an existing note on the topic first and update that instead when there is one. Example: {title: 'Meeting Notes', body: '## Agenda\n...', container_id: 5, tag_list: 'meetings, q4'}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoNote body content (Markdown with [[id:Note Title]] wiki-links)
titleYesNote title (required)
summaryNoA 2-3 sentence summary of the note. Always provide one.
team_idNoCreate note in this team instead of personal space. Omit it (or send null) for personal space.
tag_listNoComma-separated list of tags (e.g., 'ruby, rails, testing')
source_urlNoSource URL reference
container_idNoContainer ID to place the note in
review_afterNoOptional ISO 8601 datetime after which the note should be treated as stale. Use for time-boxed notes (e.g. '2026-12-31').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / team_id / description
      Previous value: -"Create note in this team instead of personal space"New value: +"Create note in this team instead of personal space. Omit it (or send null) for personal space."
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / review_after
      Added value: +{
+  "description": "Optional ISO 8601 datetime after which the note should be treated as stale. Use for time-boxed notes (e.g. '2026-12-31').",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / summary / description
      Previous value: -"Short summary of the note"New value: +"A 2-3 sentence summary of the note. Always provide one."
  4. Changed2 schema fields changed
    • changedInput schema / properties / tag_list / description
      Previous value: -"Comma-separated list of tags"New value: +"Comma-separated list of tags (e.g., 'ruby, rails, testing')"
    • changedInput schema / properties / title / description
      Previous value: -"Note title"New value: +"Note title (required)"
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint=false, destructiveHint=true, idempotentHint=false), and the description adds real value beyond them: server-enforced write access, quota notifications that email owners and cannot be recalled, and the initial status ('active'). It does not reconcile why a create tool carries destructiveHint=true, which leaves one small gap.

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?

Front-loads the operation and scope, then constraints, then optional params and an example. Dense and mostly waste-free, though the parameter recap and example add length that partly duplicates the schema.

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 an 8-parameter creation tool with no output schema, it covers access requirements, side effects, defaults, and per-parameter intent well. Return-value behavior is only partially addressed via the 'starts verified (status active)' remark.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by stating a convention the schema does not enforce ('always include a 2-3 sentence summary ... even though the schema only enforces title') and by clarifying that review_after is only for notes that should flag themselves stale.

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

Purpose5/5

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

States a specific verb and resource ('Create a note') plus the scope of targets (personal account, shared folder, team workspace), which cleanly separates it from notes-update, notes-get, and notes-list. It even names the sibling workflow to prefer when a note already exists.

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

Usage Guidelines5/5

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

Explicit routing: 'Search for an existing note on the topic first and update that instead when there is one,' which points at notes-search/notes-update. It also gives conditional guidance for individual parameters (team_id for team creation, review_after only for time-boxed notes).

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

All hjarni 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