Skip to main content
Glama
Sign In
lanhu-mcp-server

lanhu-mcp-server

by DC911360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lanhu_set_project

Extracts projectId from a Lanhu project URL or UUID and sets it as default for subsequent tool calls.

Instructions

从蓝湖项目 URL 中提取并设置默认 projectId。之后所有工具调用无需再传 projectId。支持格式：完整 URL 或直接粘贴 projectId UUID。

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": {
      "url": "<url>"
    },
    "name": "lanhu_set_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes蓝湖项目 URL 或 projectId UUID。例如：https://lanhuapp.com/web/#/item/project/detailDetach?pid=xxx&project_id=xxx

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description carries burden. It explains the effect (sets default) but lacks details on persistence, scope, or whether it overwrites. For a configuration tool, more context is needed.

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?

Two sentences, zero waste. Front-loaded with purpose and effect.

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?

Adequate for a simple configuration tool. Explains input format and outcome. Could mention whether the setting is persistent or session-based, but not essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one parameter described. Description adds an example of accepted formats (full URL or UUID), which adds value beyond the schema.

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

Purpose5/5

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

Description clearly states the tool extracts and sets a default projectId from a URL or UUID, and that subsequent calls won't need to pass projectId. This distinguishes it from sibling tools that perform design-related actions.

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?

Implied usage: use this tool before others to avoid passing projectId. However, no explicit guidance on when not to use it or alternatives for setting context.

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