gitee-mcp

gitee_help

Get Gitee MCP help to learn about available tools, tier options, configuration steps, and practical tips for efficient use.

Instructions

Gitee MCP help - tools, tiers, configuration and tips.

Return Format

{"success": bool, "help": str}

Examples

gitee_help()

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitee_help"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 18, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only mentions the return format and an example call, but does not explicitly state that the tool is read-only, safe, or requires no special permissions. The lack of transparency on side effects or restrictions leaves the agent uncertain.

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?

The description is extremely concise: one sentence stating the purpose, a clear return format header, and an example. Every element earns its place, and the critical information is front-loaded. There is no wasted text.

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?

Given the tool has no parameters, no annotations, and the description already specifies the return format and provides an example, it covers the essential information. However, it lacks guidance on when to invoke it and could elaborate on the scope of help topics (e.g., list of covered tools or configuration keys). Still, for a simple help tool, it is largely adequate.

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?

The tool has 0 parameters with 100% schema coverage. Per baseline rules, a 4 is appropriate. The description adds no parameter-level meaning (none needed), but does include return format context that aids understanding of the tool's output, which adds modest value beyond the schema.

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 clearly states the tool provides help on Gitee MCP, covering tools, tiers, configuration, and tips. It is a specific verb-resource pair (gitee_help → help), and its purpose is distinct from sibling tools like gitee_repo or gitee_search, though no explicit differentiation is provided.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or situations where another tool would be more appropriate. This omission leaves the agent without context for selection.

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

Deploy Server