Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-toggleTemplateBookmark

Idempotent

Toggles a bookmark on a Dokploy template for the authenticated user by template ID, letting users save or unsave templates they want to revisit.

Instructions

POST /user.toggleTemplateBookmark

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": {
      "templateId": "<templateId>"
    },
    "name": "user-toggleTemplateBookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the description's only contribution is the word 'POST', which weakly signals a write. Beyond that it says nothing about what state changes, whether the toggle is reversible, what permissions are needed, or what is returned. Notably, 'toggle' semantics sit awkwardly with the idempotentHint annotation, and the description offers no clarification.

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

Conciseness2/5

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

The text is short but that shortness reflects under-specification, not concision. There is no front-loaded purpose statement or structure at all, just a raw endpoint path.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, open-world, single-parameter tool with no output schema, an agent needs to know the effect of the toggle, the identifier semantics, and the authorization context. None of these are supplied and the annotations do not fill the gap, leaving the definition unusable for correct invocation.

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%, so the description must compensate for the single templateId parameter, and it does not. It gives no indication of what identifier is expected (template ID vs. bookmark ID), its format, or valid sources for the value; the agent can only infer 'template' from the tool name.

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

Purpose2/5

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

The description is the tool name rendered as an HTTP path: "POST /user.toggleTemplateBookmark" restates name and method without saying what a template bookmark is, what toggling does (add vs. remove), or whose bookmark is affected. The only addition over the title is the verb 'POST'. It is effectively a tautology rather than a purpose statement.

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

Usage Guidelines1/5

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

There is no when-to-use, when-not-to-use, or alternative guidance of any kind. An agent cannot tell from this text whether this tool is the right choice versus siblings such as user-getBookmarkedTemplates, nor whether preconditions (existing bookmark, ownership, permissions) apply.

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