Skip to main content
Glama
deenesjakoruzh
AnuragRai017

Python Docs Server

by AnuragRai017
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

python-docs-server MCP 服务器

模型上下文协议服务器

这是一个基于 TypeScript 的 MCP 服务器，它提供使用 Brave Search API 获取 Python 文档的工具。

特征

工具

  • get_python_docs - 获取给定查询的 Python 文档

    • 将搜索查询作为必需参数

    • 使用 Brave Search API 获取相关文档链接

Related MCP server: MCP2Brave

发展

安装依赖项：

npm install

构建服务器：

npm run build

对于使用自动重建的开发：

npm run watch

安装

要与 Claude Desktop 一起使用，请添加服务器配置：

在 MacOS 上： ~/Library/Application Support/Claude/claude_desktop_config.json在 Windows 上： %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "python-docs-server": {
      "command": "/path/to/python-docs-server/build/index.js"
    }
  }
}

调试

由于 MCP 服务器通过 stdio 进行通信，调试起来可能比较困难。我们推荐使用MCP Inspector ，它以包脚本的形式提供：

npm run inspector

检查器将提供一个 URL 来访问浏览器中的调试工具。

Available Tools

1 tool
get_python_docsC

Get Python documentation for a given query

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query for Python documentation

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It mentions 'Get Python documentation' but doesn't specify aspects like data sources, rate limits, authentication needs, or response formats, leaving significant gaps in understanding the tool's behavior.

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 and front-loaded, consisting of a single, clear sentence that directly states the tool's function without any unnecessary words or structural fluff.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It fails to address key contextual elements like the source of documentation, result format, or any operational constraints, making it insufficient despite the simple parameter schema.

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

Parameters3/5

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

The schema description coverage is 100%, with the single parameter 'query' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as query examples or format details, so it meets the baseline for adequate but unenriched parameter information.

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's purpose with a specific verb ('Get') and resource ('Python documentation'), and specifies the action is for a 'given query'. However, with no sibling tools mentioned, there's no opportunity to distinguish from alternatives, preventing a perfect score.

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 or any contextual prerequisites. It simply restates the basic functionality without indicating scenarios, limitations, or comparisons to other methods.

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.

  1. 1 tool update
    • First observedget_python_docs
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as retrieving Python documentation, making it distinct by default.

Naming Consistency5/5

The single tool name 'get_python_docs' follows a clear verb_noun pattern (get + python_docs). Since there is only one tool, consistency is inherently perfect with no deviations to assess.

Tool Count2/5

A single tool is too few for a server named 'Python Docs Server', which suggests a broader scope like searching, browsing, or managing documentation. One tool feels thin and limits functionality, indicating a mismatch with the apparent purpose.

Completeness2/5

The tool set is severely incomplete for a documentation server. It only provides retrieval ('get_python_docs'), lacking essential operations such as search, list topics, get specific versions, or navigate documentation structure, which are typical for such a domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches