weread-mcp

调用任意网关接口

call_gateway

Read-only

Directly invoke any WeChat Reading API endpoint when no dedicated tool exists. Automatically adds authentication headers and flattens parameters for a valid request.

Instructions

直连网关的兜底工具：当某个接口还没有对应的专用工具时使用。

    本工具会自动补上 `skill_version` 与鉴权头，并把 `params` 平铺到 body 顶层。
    能用专用工具时优先用专用工具——它们的说明里带有字段口径与避坑规则。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	业务参数，会被平铺到请求体顶层（不要再嵌套 params/data/body）
`api_name`	Yes	接口名，如 /store/search，可用 list_gateway_apis 查询

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

注释已提供readOnlyHint=true和destructiveHint=false，描述了安全轮廓。描述在此之上额外披露了行为：会自动补上skill_version与鉴权头，并把params平铺到body顶层。这些信息超出注释，有助于代理理解调用时的内部处理。没有矛盾，虽然未提及错误处理或返回格式，但输出模式已存在，此分数合理。

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?

描述分两段，第一句直接说明用途和适用条件，第二句解释自动行为和优先级建议。每个句子都有价值，无冗余，关键信息前置，结构清晰。

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

Completeness5/5

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

该工具是一个通用网关调用，复杂度中等。描述已涵盖使用场景、行为细节（自动补头和扁平化）、参数说明（通过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?

参数schema覆盖率为100%，模式本身已包含两个参数的描述（api_name的示例和params的平铺说明）。描述文本没有添加超出schema的额外语义，仅重申了平铺行为，与schema描述一致。由于schema已充分说明，基线为3，描述未额外增值。

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?

描述明确说明这是一个直连网关的兜底工具，用于当某个接口没有对应专用工具时。动词'直连'和资源'网关'清晰，与兄弟工具（如get_book_info等专用工具）形成明确区分，指出它是备用选项而非首选。目的非常清晰且能区分于其他工具。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

描述明确给出了使用时机：'当某个接口还没有对应的专用工具时使用'，并明确指示'能用专用工具时优先用专用工具'，还说明专用工具的优点（字段口径与避坑规则）。这提供了明确的when和when-not，以及替代方案，没有任何推断空间。

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