Skip to main content
Glama

derivation_show

Display the current derivation state with LaTeX formula, step count, and session info. Choose between LaTeX, SymPy, or summary format and optionally show step history.

Instructions

    顯示當前推導狀態和公式(類似 SymPy-MCP 的 print_latex_expression)

    ═══════════════════════════════════════════════════════════════════════
    ⚠️ 重要:Agent 必須在每次推導操作後調用此工具向用戶展示結果!
    ═══════════════════════════════════════════════════════════════════════

    這個工具確保用戶能看到:
    1. 當前公式的 LaTeX 渲染結果
    2. 推導進度(第幾步)
    3. 會話名稱和狀態

    Args:
        format: 輸出格式
            - "all": 完整資訊(預設)
            - "latex": 只返回 LaTeX
            - "sympy": 只返回 SymPy 字串
            - "summary": 簡短摘要
        show_steps: 是否顯示所有步驟歷史

    Returns:
        當前公式和推導狀態

    Example:
        derivation_show()
        → {
            "latex": "C_{0} e^{- k t}",
            "sympy": "C_0*exp(-k*t)",
            "session_name": "drug_elimination",
            "step_count": 3,
            "status": "active",
            "display_text": "📊 **drug_elimination** (Step 3)\n\n$$C_{0} e^{- k t}$$"
          }
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoall
session_idNo
show_stepsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description is the only source of behavioral info. It explains the output contents (LaTeX, step count, session name/status) and includes an example return object. However, it does not disclose preconditions (e.g., active session) or error behavior, leaving some transparency gaps.

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-organized with an introductory sentence, an important warning, a bulleted list of features, an Args section, Returns, and an Example. It is slightly verbose but every section adds value, except the session_id omission is not a structure issue.

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

Completeness3/5

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

Given the tool's simplicity, the description covers purpose, usage, most parameters, and output format via the example. It falls short on explaining the session_id parameter and does not address error scenarios or prerequisites. Overall, it is adequate but not fully complete.

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

Parameters2/5

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

The description documents the 'format' parameter with its four values and 'show_steps' with its meaning, but completely omits 'session_id'. Since schema description coverage is 0%, this omission means one of three parameters is entirely unexplained, which is a significant gap.

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 clearly states the tool's function: displaying the current derivation state and formula, with an explicit comparison to SymPy-MCP's print_latex_expression. The warning that agents must call it after every derivation operation further distinguishes it as the primary display tool among many derivation siblings.

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 states 'Agent must call this tool after every derivation operation to show results to the user', which provides a clear usage context. It does not explicitly mention exclusions or alternative tools, but the guidance is unambiguous.

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