Skip to main content
Glama

noteking_reorder_pinned

Reorder pinned notes in the NoteKing sidebar by supplying an ordered list of note IDs to set their display sequence.

Instructions

Update the sequential order of pinned notes displayed in the NoteKing sidebar

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": {
      "note_ids": "<note_ids>"
    },
    "name": "noteking_reorder_pinned"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idsYesOrdered list of pinned note IDs representing the new sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations present, the description carries the full burden and discloses little. It does not say whether the list must contain every currently pinned note, what happens to pinned notes omitted from the list, whether the operation is atomic or reversible, or what errors occur for IDs that are not pinned.

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?

One front-loaded sentence with no padding and no wasted clauses. It is efficient, though the phrase 'displayed in the NoteKing sidebar' is mild restatement of what reordering implies.

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?

For an unannotated mutation with no output schema, an agent still cannot determine list-completeness semantics, partial-failure behavior, or return value. The description identifies the intent but leaves the operational contract underspecified.

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?

The single parameter is fully documented in the schema as an ordered list of pinned note IDs for the new sequence. The description adds only the confirmation that these are pinned notes shown in the sidebar, which is marginal but consistent with a 100%-coverage schema baseline of 3.

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: setting the sequential order of pinned notes in the NoteKing sidebar. This is clearly distinguishable from a generic note update, though it never names noteking_toggle_pin or explains which one to reach for when merely re-pinning.

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?

There is no when-to-use or when-not-to-use guidance, no preconditions, and no mention of the closely related noteking_toggle_pin sibling. An agent must infer that this only applies after notes are already pinned.

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