pkulaw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PKULAW_TOKEN | Yes | Your 北大法宝 (PKULaw) Token. Provide only the token itself; do not add a 'Bearer ' prefix, spaces, or newlines. It must be passed via the PKULAW_TOKEN environment variable to the runtime. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pkulaw_list_upstream_toolsA | 使用本实例用户自己的法宝凭据读取官方聚合MCP真实工具名称和schema。无凭据将失败；不是公开匿名服务。可用nextCursor分页。 |
| pkulaw_call_upstream_toolA | 按pkulaw_list_upstream_tools返回的真实name/schema调用官方工具。arguments不可放入凭据；凭据仅由实例环境配置。本工具不是18个原生工具的schema直通。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one discovers upstream tool names and schemas, the other invokes them. The descriptions explicitly clarify the relationship and prevent confusion between listing and calling.
Both names use a consistent pkulaw_ prefix and verb_noun structure (list_upstream_tools, call_upstream_tool). There is a minor singular/plural mismatch between 'tools' and 'tool', but the pattern remains predictable.
Two meta-tools are appropriate for a gateway/proxy server whose real surface is discovered dynamically. The count is slightly below the typical 3-15 range, but each tool earns its place and avoids unnecessary duplication.
The list-and-call pair covers the core proxy lifecycle: discover upstream schemas and invoke them. Minor gaps exist around explicit credential status or single-tool metadata, but the list tool returns the necessary schemas for invocation.