Skip to main content
Glama

formula_search

Search the local formula library to retrieve accurate mathematical and physical formulas by keyword or domain.

Instructions

Search the local formula library.

    Retrieve accurate mathematical/physical formulas from the local, editable
    YAML library. This is deterministic, fast, and does not require network
    access.

    The query and domain are normalized automatically, so you can pass
    free-form text such as "Navier–Stokes equations" or "fluid_dynamics".

    Args:
        query: Search keyword
               - English name: "Reynolds number", "Arrhenius equation"
               - Domain terms: "fluid dynamics", "quantum", "thermodynamics"
        source: Data source
               - "local": Local YAML library (default, recommended)
               - "scipy": Physical constants only (no local search)
               - "legacy": Search local, then Wikidata, BioModels, SciPy
               - "all": Alias for "legacy" (kept for compatibility)
               - "wikidata", "biomodels", "scipy": Legacy source only
        domain: Restrict domain (optional)
               - "mechanics", "thermodynamics", "electromagnetism"
               - "fluid_dynamics", "fluid_mechanics", "quantum_mechanics"
        limit: Maximum number of results to return

    Returns:
        {
            "success": true,
            "results": [...],
            "total": 1,
            "query": "navier-stokes equations",
            "domain": "fluid",
            "sources_searched": ["local"],
            "next_steps": [...]
        }

    Example:
        # Search the local library
        formula_search("Reynolds number")

        # Search by domain
        formula_search("diffusion", domain="thermodynamics")

    Correct workflow for derivation:
        1. formula_search("<concept>", domain="<domain>")
        2. formula_get(result["id"])
        3. session_load_formula(formula["sympy_str"] or formula["latex"], ...)
        4. math(..., session=True) to derive or transform
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
domainNo
sourceNolocal

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 states that the search is 'deterministic, fast, and does not require network access' and mentions automatic normalization of queries. It doesn't mention destructive actions or auth needs, but as a read-only search tool, this is adequate.

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 long but well-organized with sections, examples, and a workflow. It front-loads the purpose and then details parameters and usage. While every sentence is valuable, some repetition in source descriptions could be trimmed.

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?

Given the complexity (4 parameters, no schema descriptions, output schema present), the description is highly complete. It includes parameter explanations, example workflows, and even a sample return format, leaving little ambiguity for the agent.

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?

With schema description coverage at 0%, the description must explain parameters. It provides extensive details for each parameter: query (with examples), source (with all valid values), domain (optional with examples), and limit (though minimal). This fully compensates for the lack of schema descriptions.

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 'Search the local formula library' and details the function of retrieving formulas from a YAML library. It distinguishes this tool from siblings like formula_get (which retrieves by ID) by focusing on search functionality and providing a workflow.

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 includes a 'Correct workflow for derivation' that shows when to use this tool as the first step. It also explains different source options (local, scipy, legacy) and recommends 'local' as default. It doesn't explicitly state when not to use this tool, but the workflow suggests it's for initial search, not for retrieving specific formulas already known.

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