Skip to main content
Glama

formula_get

Retrieve detailed formula information from the local library or legacy sources. Optionally load the formula into an active derivation session for step-by-step symbolic computation.

Instructions

Get detailed formula information from the local library.

    Args:
        formula_id: Formula identifier (e.g., "reynolds_number")
        source: Data source
               - "local": Local YAML library (default, recommended)
               - "wikidata", "biomodels", "scipy": Legacy sources
        load_into_session: If True, load the formula into the current derivation session.
                          Requires an active session started with session_start().

    Returns:
        {
            "success": true,
            "formula": {
                "id": "reynolds_number",
                "name": "Reynolds number",
                "latex": "Re = \frac{\rho v L}{\mu}",
                "sympy_str": "rho * v * L / mu",
                "variables": {...},
                "source": "local"
            },
            "session_loaded": true
        }

    Example:
        # Get a local formula
        formula_get("reynolds_number")

        # Get and immediately load into a derivation session
        formula_get("reynolds_number", load_into_session=True)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNolocal
formula_idYes
load_into_sessionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so description carries full burden. It discloses that loading into session requires an active session started with session_start(). Return format is shown. Safe read operation implied.

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?

Well-structured with Args, Returns, and Example sections. Each sentence earns its place, though default values are redundantly restated from schema.

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

Completeness5/5

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

Complete for the tool's complexity: all three parameters explained, return object detailed, and example usage provided. Output schema exists, so description complements it well.

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?

Schema has 0% description coverage, but the description fully explains each parameter: formula_id with example, source with enum values and recommendation, and load_into_session with prerequisite. Adds significant meaning beyond schema.

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 states 'Get detailed formula information from the local library'—a specific verb+resource. It distinguishes from sibling tools like formula_search and formula_add by focusing on retrieval and immediate session loading.

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?

Provides clear context: use to get formula details, with guidance on source options and loading into session. Lacks explicit when-not-to-use but adequate given sibling diversity.

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