Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Update project

openpanel_update_project
Destructive

Update an existing OpenPanel project's name or domain through the Manage API in root mode. Use it to rename a project or point it to a new domain.

Instructions

[UNIFIED] Update a project via Manage API. Requires 'root' mode client.

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": {
      "site": "<site>",
      "project_id": "<project_id>"
    },
    "name": "openpanel_update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
siteYes
domainNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so safety is covered structurally. The description adds useful auth context (root-mode client requirement) but says nothing about partial-vs-full update semantics, what happens to omitted fields like name/domain, or reversibility.

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?

Two short sentences with the requirement front-loaded and nothing redundant. The bracketed '[UNIFIED]' prefix is noise that does not help an agent decide or call correctly.

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 a destructive mutation with no output schema and zero parameter documentation, the description should at minimum describe the updatable fields and the effect of null values. The auth prerequisite is the only real content beyond the name restatement.

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% and the description never mentions any of the four parameters. It does not explain what 'site' vs 'project_id' identify, or what setting name/domain to null means, so the caller must infer everything from bare types and defaults.

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 ('Update a project') plus the API surface ('Manage API'), so the operation is identifiable. It does not distinguish itself from openpanel_create_project/delete_project/get_project, the closest siblings, and the '[UNIFIED]' tag is unexplained jargon that adds ambiguity rather than clarity.

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?

The 'Requires root mode client' line gives a genuine prerequisite, which is the main selection signal. There is no statement of when to prefer this over create/delete/get siblings, and no exclusions or failure conditions.

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