Skip to main content
Glama
darcycui

DarcyAIMCPServer

by darcycui

是什么

Python语言,基于 mcp 库实现的一个 MCP-Server。

Related MCP server: Weather MCP Server

有什么能力

预测明天的天气。

怎么用

远程使用 (推荐)

  1. 如果未安装 uv工具,先执行一键安装脚本安装

    # 在 macOS 上安装
    # 推荐使用 Homebrew 安装:
    brew install uv
    # 或者使用官方安装脚本:
    curl -LsSf https://astral.sh/uv/install.sh | sh

    # 在 Linux 上安装
    curl -LsSf https://astral.sh/uv/install.sh | sh

    # 在 Windows 上安装
    # 使用 Winget:
    winget install uv
    # 或者使用官方安装脚本(PowerShell):
    irm https://astral.sh/uv/install.ps1 | iex

    # 安装完成后,验证是否成功:
    uv --version
  1. 添加如下 mcpServers 配置

    {
      "mcpServers": {
        "weather": {
          "autoApprove": [],
          "disabled": false,
          "timeout": 60,
          "type": "stdio",
          "command": "uvx",
          "args": [
            "darcycui-mcp"
          ]
        }
      }
    }

本地使用

  1. clone项目到本地 path

  2. 添加如下配置

  3. 注意 path 替换为你的本地路径

  4. 注意 路径分隔符,Linux/Mac 使用/分隔符, Windows 使用\分隔符

    {
      "mcpServers": {
        "weather": {
          "autoApprove": [],
          "disabled": true,
          "timeout": 60,
          "type": "stdio",
          "command": "uv",
          "args": [
            "--directory",
            "path\\src\\darcycui_mcp",
            "run",
            "weather.py"
          ]
        }
      }
    }

运行结果

运行结果

参考文章

马克的技术工坊Github

MCP终极指南 - 从原理到实战,带你深入掌握MCP(基础篇)-哔哩哔哩

MCP终极指南 - 带你深入掌握MCP(进阶篇)-哔哩哔哩

一文搞懂MCP、Function Calling和A2A

Available Tools

1 tool
get_forecastC
获取天气信息
:param city: 城市名称
:return: 天气信息
ParametersJSON Schema
NameRequiredDescriptionDefault
cityYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It only states that the tool fetches weather information, but discloses no behavioral traits such as data source, freshness, or limitations. There is no mention of side effects or required permissions.

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

Conciseness3/5

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

The description is short and front-loaded with the main sentence, but the docstring format adds a little structure. However, it is under-specified for a tool with no annotations and an output schema. Every sentence is earned but more detail would be beneficial.

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

Completeness3/5

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

Given the tool has one required parameter and an output schema (not shown), the description provides the basic purpose. It does not explain the return value beyond ':return: 天气信息', which is insufficient for understanding the expected output without viewing the schema. Overall adequate but with clear gaps.

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. The ':param city: 城市名称' line merely repeats the parameter name and title without adding formatting constraints, allowed values, or input examples. This adds minimal 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 '获取天气信息' (Get weather information) clearly states the verb (获取/get) and resource (天气信息/weather information), matching the tool name 'get_forecast'. While it is clear, it does not differentiate from any sibling tools, as none are listed.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention when not to use it. There is no context about prerequisites or typical use cases.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.5
    • First observedget_forecast

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as getting weather forecasts.

Naming Consistency5/5

The single tool name 'get_forecast' follows a clear verb_noun pattern with snake_case, which is consistent and predictable.

Tool Count2/5

A server ostensibly about weather forecasting with only one tool is overly limited. Typically, even a minimal weather server would include multiple tools (current, forecast, etc.).

Completeness2/5

The tool set is severely incomplete for weather information. It only provides forecasts, missing current conditions, historical data, or alerts, which are standard for such a domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/darcycui/DarcyAIMCPServer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server