Skip to main content
Glama

企业微信应用号-发送文件消息

wework_app_send_file

Send file messages to WeWork members via corporate app. Provide a file URL and optionally specify recipient IDs or send to all.

Instructions

通过企业微信应用号发送发送文件消息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes文件URL
touserNo接收消息的成员ID,多个用`|`分隔,为`@all`时向该企业应用全部成员发送,默认从环境变量获取

Implementation Reference

  • Handler function for the 'wework_app_send_file' tool. Decorated with @mcp.tool. Accepts a file URL and optional touser, then delegates to wework_send_media() with msgtype='file'.
    @mcp.tool(
        title="企业微信应用号-发送文件消息",
        description="通过企业微信应用号发送发送文件消息",
    )
    def wework_app_send_file(
        url: str = Field(description="文件URL"),
        touser: str = FIELD_TO_USER,
    ):
        return wework_send_media(touser, url, "file")
  • Helper function that downloads media from a URL, uploads it to WeWork's media API to get a media_id, then sends it as a message via the WeWork app. Used by wework_app_send_file (and wework_app_send_image/video/voice).
    def wework_send_media(touser, url: str, msgtype=None):
        if msgtype:
            pass
        elif '.jpg' in url.lower() or '.jpeg' in url.lower() or '.png' in url.lower():
            msgtype = 'image'
        elif '.mp4' in url.lower():
            msgtype = 'video'
        elif '.arm' in url.lower():
            msgtype = 'voice'
        else:
            msgtype = 'file'
        res = requests.get(url, timeout=120)
        res.raise_for_status()
        file = io.BytesIO(res.content)
        mine = res.headers.get("content-type") or "application/octet-stream"
        res = requests.post(
            f"{WEWORK_BASE_URL}/cgi-bin/media/upload",
            params={"type": msgtype, "access_token": get_access_token()},
            files={"media": ("filename", file, mine)},
            timeout=120,
        )
        media = res.json() or {}
        if not (media_id := media.get("media_id")):
            return media
        res = requests.post(
            f"{WEWORK_BASE_URL}/cgi-bin/message/send?access_token={get_access_token()}",
            json={
                "touser": touser or WEWORK_APP_TOUSER,
                "agentid": WEWORK_APP_AGENTID,
                "msgtype": msgtype,
                msgtype: {"media_id": media_id},
            },
        )
        return res.json()
  • Tool registration entry point. The wework module is imported and its add_tools(mcp) function is called in __init__.py, which registers all wework tools (including wework_app_send_file) onto the FastMCP server.
    from . import (
        wework,
        tgbot,
        other,
        hass,
        util,
    )
    
    _LOGGER = logging.getLogger(__name__)
    
    
    mcp = FastMCP(name="mcp-notify", version="0.1.11")
    wework.add_tools(mcp)
    tgbot.add_tools(mcp)
    other.add_tools(mcp)
    hass.add_tools(mcp)
    util.add_tools(mcp)
  • The wework.add_tools() function that registers all tools including wework_app_send_file onto the FastMCP instance via the @mcp.tool decorator.
    def add_tools(mcp: FastMCP, logger=None):
    
        @mcp.tool(
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as file size limits, supported formats, or side effects. It merely says 'send file message' without any behavioral details.

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

Conciseness4/5

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

The description is a single sentence, very concise and front-loaded with the action. However, it lacks structure (e.g., bullet points) and contains a typo, but overall efficient.

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 no output schema, the description should at least hint at return values or confirmation. It does not, leaving the agent without knowledge of success/failure behavior. For a mutation tool, this is insufficient.

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 description coverage is 100%, so the description adds no new meaning beyond the schema. The short description does not enhance understanding of parameters, but it does not contradict the schema either.

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 it sends a file message via WeChat Work app, distinguishing it from sibling tools for other message types (text, image, news, etc.) and other platforms. However, there is a minor typo ('发送发送') and no further detail on file capabilities.

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?

No guidance is provided on when to use this tool vs. other WeChat Work send tools or alternatives like 'wework_app_send_text'. Prerequisites like authentication or app ID are not mentioned.

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

Install Server

Other Tools

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/aahl/mcp-notify'

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