Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_reorder_pinned

Reorder pinned prompts in the Devbook sidebar by supplying an ordered list of prompt IDs to set their new display sequence.

Instructions

Update the sequential order of pinned prompts displayed in the Devbook 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": {
      "prompt_ids": "<prompt_ids>"
    },
    "name": "devbook_reorder_pinned"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_idsYesOrdered list of pinned prompt 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?

No annotations are supplied, so the description carries the full burden and falls short: it does not say whether the list fully replaces the existing order, what happens to pinned prompts left out of the array, whether it fails on unpinned or nonexistent IDs, or whether changes are persisted immediately. Only the vague notion of sidebar display order is conveyed.

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 well-formed sentence with the action front-loaded and no filler. Its brevity is appropriate, though the tight phrasing is also where the missing behavioral detail lies.

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 one-parameter, non-destructive-looking ordering tool with no output schema, the definition is minimally sufficient. It is nonetheless silent on whether the array must be exhaustive and on error conditions, which matters for an ordering operation that replaces state.

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 coverage is 100% and the single parameter's schema description already states it is an ordered list of pinned prompt IDs defining the new sequence. The description adds the sidebar-display framing but no new constraint such as completeness of the list or behavior on omitted IDs.

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?

Names a specific verb and resource — updating the sequential order of pinned prompts in the sidebar — which is clearly distinct from a general prompt update. It does not explicitly contrast with the closely related devbook_toggle_pin, so the agent must infer the boundary.

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 guidance on when to call this versus devbook_toggle_pin, nor any stated prerequisite that the prompts must already be pinned. The agent gets a purpose but no selection criteria or preconditions.

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

Deploy Server

Other Tools