Skip to main content
Glama
LBurny

SymKit

by LBurny
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

derive

Start a mathematical derivation by describing a goal in natural language. Get a derivation plan, recommended formulas, and next steps.

Instructions

    🚀 High-level derivation entry point — start a derivation from a goal.

    Args:
        goal: Natural-language description of what to derive
        given: Base formulas or expressions to load as starting points
        assumptions: List of assumptions (e.g., ["rho is positive"])
        domain: Math/physics domain (e.g., "fluid_dynamics")
        pattern: Derivation pattern. If None, auto-selected from goal.
        target_expression: Expected final SymPy expression (optional)
        auto_load: If True, load the given formulas into the session
        external_sources: External formula sources to include in recommendations
            (e.g., ["wikidata", "biomodels", "scipy"] or ["all"]).
            Defaults to all sources; network failures are silently ignored.

    Returns:
        Session info + goal + derivation plan + recommended formulas + next steps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYes
givenNo
domainNogeneral
patternNo
auto_loadNo
assumptionsNo
external_sourcesNo
target_expressionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the return values and notes that external_sources defaults to all sources and network failures are silently ignored. However, it does not disclose potential side effects (e.g., session creation), authorization needs, or the full behavioral impact beyond the listed parameters.

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 an emoji lead-in, an Args list, and a Returns line. It is concise, with each sentence earning its place. Could be slightly more compact, but overall efficient.

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 complexity (8 parameters, 1 required) and no annotations, the description is adequate but incomplete. It explains parameters and return values, but does not cover prerequisites (e.g., session existence), error conditions, or the overall flow. The returns are summarized but could be more specific.

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 description provides a comprehensive list of all 8 parameters with one-line explanations, compensating for the 0% schema description coverage. Each parameter is explained in natural language, adding meaning beyond the schema types and default values.

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 is a high-level derivation entry point that starts a derivation from a goal. This specific verb+resource combination distinguishes it from sibling tools like session_start or formula_search, which have different purposes.

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 explicit guidance on when to use this tool versus alternatives. Siblings include session_start, session_set_goal, and others that could be confused, but the description does not clarify the appropriate context or provide when-not-to-use advice.

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/LBurny/symkit-mcp'

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