Skip to main content
Glama

derivation_export_for_sympy

Export current derivation state to SymPy-MCP, including variables, expression, and next-step suggestions for advanced symbolic computation.

Instructions

    導出當前推導狀態給 SymPy-MCP

    ═══════════════════════════════════════════════════════════════════════
    🔄 HANDOFF 機制 - 當 NSForge 無法處理時,交給 SymPy-MCP!
    ═══════════════════════════════════════════════════════════════════════

    使用時機:
    - 需要解 ODE/PDE
    - 需要矩陣運算
    - 需要複雜的 SymPy 操作(如 limit, series, dsolve)
    - NSForge 工具返回錯誤時

    這個工具會輸出:
    1. 所有已定義的變數(可直接貼到 intro_many)
    2. 當前表達式(可直接貼到 introduce_expression)
    3. 建議的下一步操作

    Returns:
        包含可直接使用的 SymPy-MCP 指令

    Example:
        # NSForge 中遇到無法處理的操作
        derivation_export_for_sympy()
        → {
            "intro_many_command": "intro_many(['k', 'T', 'Ea', 'R'], 'real positive')",
            "current_expression": "k * exp(-Ea/(R*T))",
            "suggested_actions": [...]
          }

        # 然後在 SymPy-MCP 中執行
        intro_many(['k', 'T', 'Ea', 'R'], 'real positive')
        introduce_expression("k * exp(-Ea/(R*T))", "arrhenius")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNo
include_variablesNo
include_current_expressionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the output structure (variables, current expression, suggested actions) and provides a concrete example of the return value. However, it does not explicitly state whether the tool is read-only or any side effects on the derivation session, though 'export' implies non-mutating.

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 headers, a use-case list, and an example, making it scannable. The decorative formatting (═══ lines, emoji) adds visual noise but doesn't detract significantly. It is slightly longer than necessary but each section adds value.

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?

The description provides purpose, usage guidance, output description, and a complete example, which covers the essential context for an agent. It doesn't elaborate on session_id handling or failure modes, but given the tool's simple export responsibility and the presence of an output schema, the description is reasonably complete.

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 0%, so the description must compensate. It explains that the tool outputs all defined variables and the current expression, which maps to include_variables and include_current_expression, but it never mentions the session_id parameter or how it affects behavior. The example shows the output format but doesn't clarify the parameters' roles comprehensively.

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?

The description opens with a clear statement: '導出當前推導狀態給 SymPy-MCP' (Export current derivation state to SymPy-MCP), which specifies the verb and resource. The 'HANDOFF 機制' header further distinguishes this from siblings by positioning it as the bridge to SymPy-MCP when NSForge cannot handle an operation.

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?

The '使用時機' (usage timing) section explicitly lists four use cases: solving ODE/PDE, matrix operations, complex SymPy operations, and when NSForge tools return errors. This provides clear context and implicitly contrasts with the sibling NSForge tools, giving an agent concrete guidance on when to invoke this tool.

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/u9401066/nsforge-mcp'

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