Skip to main content
Glama

formula_search

Retrieve accurate scientific formulas from Wikidata, BioModels, and SciPy. Search by name or domain to get equations with LaTeX and SymPy representations.

Instructions

    搜尋公式(跨多個來源)

    這是科學運算 Agent 的核心工具,可從多個權威來源檢索準確的公式。
    使用直接精確檢索(非 RAG),確保公式正確性。

    Args:
        query: 搜尋關鍵字
               - 英文名稱: "Reynolds number", "Arrhenius equation"
               - 領域術語: "pharmacokinetics", "Michaelis-Menten"
        source: 資料來源
               - "all": 搜尋所有來源(預設)
               - "wikidata": 僅 Wikidata(跨領域)
               - "biomodels": 僅 BioModels(藥學/生物)
               - "scipy": 僅 SciPy 常數
        domain: 限定領域(可選)
               - "mechanics", "thermodynamics", "electromagnetism"
               - "pharmacokinetics", "pharmacodynamics", "enzyme_kinetics"
        limit: 返回數量上限

    Returns:
        {
            "success": true,
            "results": [
                {
                    "id": "Q179057",
                    "name": "Reynolds number",
                    "latex": "Re = \frac{\rho v L}{\mu}",
                    "sympy_str": "rho * v * L / mu",
                    "source": "wikidata",
                    "url": "https://www.wikidata.org/wiki/Q179057"
                }
            ],
            "total": 1,
            "sources_searched": ["wikidata"]
        }

    Example:
        # 搜尋雷諾數
        formula_search("Reynolds number")

        # 搜尋藥動學模型
        formula_search("one compartment", source="biomodels")

        # 按領域搜尋
        formula_search("diffusion", domain="thermodynamics")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
domainNo
sourceNoall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the direct non-RAG retrieval method, source options, and return schema, which is valuable context. It omits error handling and rate limits, but for a search tool the key behaviors are well-covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with a one-line summary, Args section, Returns schema, and examples. Every part earns its place without redundancy or unnecessary filler.

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?

Despite no annotations, the description covers query syntax, source selection, domain filtering, output format, and usage examples. It even includes the response schema. Minor omissions like error handling or pagination are not critical for this search tool.

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 description coverage is 0%, so the description must compensate. It thoroughly explains each parameter: query format with examples, source enumeration, domain domain values, and limit behavior. Returns and examples further clarify parameter usage.

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 searches formulas across multiple authoritative sources, positioning it as the core scientific computing tool. It distinguishes itself from siblings like formula_get by emphasizing cross-source search and direct exact retrieval.

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 explains the tool is the core search mechanism and provides realistic examples across formula types and domains. However, it doesn't explicitly mention when not to use it or name alternatives, so it stops short of full exclusion guidance.

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