Skip to main content
Glama

ui_save_note

Create or update a project or task note from the UI, including decisions, gotchas, specs, and general notes, so context stays attached to the right work item.

Instructions

App-only: create or update a project/task note from the UI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "title": "<title>",
      "body_markdown": "<body_markdown>"
    },
    "name": "ui_save_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
titleYes
pinnedNo
note_idNo
task_idNo
project_idYes
body_markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It hints at upsert behavior ("create or update") and UI scope, but says nothing about what an update replaces (does body_markdown overwrite wholesale?), how note_id versus task_id selects the mode, or whether pinned/kind are preserved or reset.

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?

A single front-loaded sentence with the most important constraint ("App-only") first and zero filler. Its brevity is efficient structure, though it borders on under-specification for a 7-parameter mutation tool.

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?

Seven parameters, no annotations, no output schema, and no parameter documentation mean the description needs to do heavy lifting, and one line is not enough. An agent cannot determine update-versus-create semantics, overwrite behavior, or return shape from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven parameters, so the description must compensate and largely doesn't. The words "project/task note" loosely map to project_id and task_id, and "update" hints that note_id is the update key, but kind, pinned, and the empty-string-vs-null task_id case are unaddressed.

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?

"App-only: create or update a project/task note from the UI" gives a specific verb pair and resource, and the "App-only/from the UI" qualifier signals it is the UI-surface variant rather than a general note API. It never names a sibling (e.g. note_save), so the distinction is implied rather than stated.

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?

"App-only" implies a usage boundary — this is for UI-driven writes, not programmatic ones — which is real guidance. However, there is no explicit when-to-use/when-not and no named alternative for the non-UI case, leaving the agent to infer the routing decision.

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