Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_toggle_pin

Toggle whether a Devbook prompt is pinned in the sidebar by providing its ID, so you can control which prompts stay accessible.

Instructions

Toggle the pinned status of a prompt on 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": {
      "id": "<id>"
    },
    "name": "devbook_toggle_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the prompt whose pin status to toggle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 entire behavioral burden for a mutation. "Toggle" does disclose that the operation flips state rather than setting an absolute value, but nothing is said about whether the change is reversible by a repeat call, what permissions are needed, what happens on an already-in-the-target-state prompt, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the verb and resource, with zero filler or redundant restatement of the tool name.

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 one-parameter, non-nested tool with full schema coverage and no output schema, the description covers enough for correct invocation. The only real gap is that it does not state the post-toggle state (or returned result) the caller should expect.

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 description coverage is 100% and the single parameter is documented in the schema as "Unique identifier of the prompt whose pin status to toggle", which is effectively the same wording the description uses. The description adds no new meaning (no format, range, or origin hints), so the baseline 3 applies.

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?

The description pairs a specific verb ("Toggle") with a specific resource ("pinned status of a prompt") and a location ("Devbook sidebar"), so an agent can immediately tell this is a pin-state mutation rather than a prompt CRUD operation. It stops short of naming a sibling such as devbook_reorder_pinned, so sibling differentiation is only implicit.

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?

Usage is implied by the self-describing name and the single required id: call it to flip a prompt's pin on or off. There is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no indication of how this relates to devbook_reorder_pinned for reordering pinned items.

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