Skip to main content
Glama
Alex-Smith-1234

讯飞智文PPT生成服务MCP Server

create_outline

Generate PowerPoint presentation outlines from text content for use with PPT creation tools, with optional online search to supplement information.

Instructions

创建PPT大纲。

使用说明:
1. 用于根据文本内容生成PPT大纲。
2. 生成的大纲可用于create_ppt_by_outline工具。
3. 可通过search参数控制是否联网搜索补充内容。
4. 需先设置环境变量AIPPT_APP_ID和AIPPT_API_SECRET。

参数:
- text: 需要生成大纲的内容描述。
- language: 大纲生成的语言,目前支持cn(中文)。
- search: 是否联网搜索,True表示联网搜索补充内容,False表示不联网。

返回:
包含生成的大纲内容的字典。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
languageNocn
searchNo

Implementation Reference

  • The handler function for the 'create_outline' MCP tool. It is decorated with @mcp.tool() which registers it and auto-generates schema from the signature and docstring. The function calls the external ZwAPI to create a PPT outline based on input text.
    @mcp.tool()
    def create_outline(
        ctx: Context,
        text: str,
        language: str = "cn",
        search: bool = False
    ) -> Dict[str, Any]:
        """
        创建PPT大纲。
        
        使用说明:
        1. 用于根据文本内容生成PPT大纲。
        2. 生成的大纲可用于create_ppt_by_outline工具。
        3. 可通过search参数控制是否联网搜索补充内容。
        4. 需先设置环境变量AIPPT_APP_ID和AIPPT_API_SECRET。
        
        参数:
        - text: 需要生成大纲的内容描述。
        - language: 大纲生成的语言,目前支持cn(中文)。
        - search: 是否联网搜索,True表示联网搜索补充内容,False表示不联网。
        
        返回:
        包含生成的大纲内容的字典。
        """
        url = "https://zwapi.xfyun.cn/api/ppt/v2/createOutline"
        form_data = MultipartEncoder(
            fields={
                "query": text,
                "language": language,
                "search": str(search)
            }
        )
        headers = get_headers(form_data.content_type)
        response = requests.post(url, data=form_data, headers=headers)
    
        if response.status_code != 200:
            raise Exception(f"调用失败: {response.text}")
    
        return response.text
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool can perform web searches (via the 'search' parameter) and requires environment variables for authentication, which are useful behavioral traits. However, it doesn't cover other aspects like rate limits, error handling, or what happens during the outline generation process, leaving gaps in behavioral context.

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 well-structured with sections for purpose, usage instructions, parameters, and returns, making it easy to scan. It's appropriately sized with no redundant sentences, though the Chinese language might add slight complexity for non-native agents, but the content is front-loaded and efficient.

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

Completeness4/5

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

Given the tool has 3 parameters, no annotations, and no output schema, the description does a good job covering key aspects: purpose, usage, parameters, and return format. It mentions prerequisites and sibling tools, but could improve by detailing output structure or error cases more explicitly, given the lack of structured output schema.

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

Parameters5/5

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

The schema description coverage is 0%, so the description must compensate fully. It adds significant meaning beyond the input schema by explaining each parameter: 'text' is for content description, 'language' specifies supported options (currently 'cn'), and 'search' controls web searching with boolean semantics. This provides clear semantics that the schema alone lacks.

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 as '创建PPT大纲' (create PPT outline) and specifies it generates outlines from text content, which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'create_outline_by_doc' which likely serves a similar purpose with different input, leaving room for improvement.

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

Usage Guidelines4/5

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

The description provides clear usage context: it indicates when to use this tool (for generating outlines from text) and mentions an alternative tool 'create_ppt_by_outline' for subsequent steps. It also notes prerequisites (setting environment variables). However, it lacks explicit guidance on when not to use it or comparisons with other siblings like 'create_outline_by_doc'.

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/Alex-Smith-1234/zwppt-mcp'

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