Skip to main content
Glama
enesjakozh
SecretiveShell

MCP-wolfram-alpha

by SecretiveShell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP-wolframio-alfa

Un servidor MCP para conectarse a la API de Wolfram Alpha.

Componentes

Indicaciones

Esto es análogo al !wa bang en la búsqueda de duckduckgo.

def wa(query: str) -> f"Use wolfram alpha to answer the following question: {query}"

Herramientas

Consulta la API de Wolfram Alpha.

def query_wolfram_alpha(query: str) -> str

Related MCP server: Wolfram Alpha MCP Server

Configuración

Debe configurar la variable de entorno WOLFRAM_API_KEY . Obtenga una clave API de Wolfram Alpha .

Esto se probó con la API de resultados completa, pero es posible que no sea necesario.

{
    "mcpServers": {
        "MCP-wolfram-alpha": {
            "command": "uv",
            "args": [
                "--directory",
                "C:\\Users\\root\\Documents\\MCP-wolfram-alpha",
                "run",
                "MCP-wolfram-alpha"
            ],
            "env": {
                "WOLFRAM_API_KEY": "your-app-id"
            }
        }
    }
}

Desarrollo

Depuración

Dado que el inspector oficial de MCP no tiene un buen soporte de entorno, recomiendo utilizar mcp-cli-inspector de wong2.

Crea un archivo config.json con el mismo estilo que Claude Desktop.

{
    "mcpServers": {
        "MCP-wolfram-alpha": {
            "command": "uv",
            "args": [
                "--directory",
                "/full/path/to/MCP-wolfram-alpha",
                "run",
                "MCP-wolfram-alpha"
            ],
            "env": {
                "WOLFRAM_API_KEY": "your-app-id"
            }
        }
    }
}

Luego ejecuta:

npx @wong2/mcp-cli -c .\config.json

Available Tools

1 tool
query-wolfram-alphaB

Use Wolfram Alpha to answer a question. This tool should be used when you need complex math or symbolic intelligence.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes

TDQS

B3.2/5.0
Behavior2/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 of behavioral disclosure. The description mentions the tool's purpose but doesn't disclose important behavioral traits such as rate limits, authentication requirements, response format, or error handling. It adds minimal value beyond stating what the tool does.

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 appropriately sized and front-loaded with the core purpose in the first sentence and usage guidance in the second. Both sentences earn their place by providing essential information without waste.

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

Completeness2/5

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

Given the tool's complexity (querying an external API for complex computations), lack of annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't address how results are returned, error conditions, or practical constraints, leaving significant gaps for an AI agent.

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 input schema has 1 parameter with 0% description coverage. The description doesn't add any meaning about the 'query' parameter beyond what's implied by the tool's purpose. It doesn't explain what constitutes a valid query, format expectations, or examples, failing to compensate for the low schema coverage.

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 the tool's purpose: 'Use Wolfram Alpha to answer a question.' It specifies the action ('answer a question') and the resource (Wolfram Alpha). However, it doesn't distinguish from siblings since there are none, so it can't achieve a perfect 5.

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 provides clear context on when to use this tool: 'when you need complex math or symbolic intelligence.' This gives explicit guidance on appropriate use cases. However, it doesn't mention when NOT to use it or name alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedquery-wolfram-alpha
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as querying Wolfram Alpha for complex math or symbolic intelligence, making it distinct by default.

Naming Consistency5/5

The single tool name 'query-wolfram-alpha' follows a consistent verb-noun pattern, using kebab-case. Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.

Tool Count2/5

One tool is too few for a server named 'MCP-wolfram-alpha', which suggests broader Wolfram Alpha integration. A single query tool feels thin and limits functionality, as it lacks operations like data retrieval, visualization, or specialized computations that might be expected from such a service.

Completeness2/5

The tool surface is severely incomplete for a Wolfram Alpha integration. While the query tool handles basic questions, there are obvious gaps such as no support for step-by-step solutions, data analysis, image generation, or API-specific features like units conversion or historical data, which are core to Wolfram Alpha's capabilities.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Wolfram Alpha MCP Server

    heesookiim
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables users to query Wolfram Alpha's computational knowledge engine through natural language. Provides access to mathematical computations, scientific data, and factual information via the Wolfram Alpha API.
    -

  • Wolfram Alpha MCP Server

    xiaomayisjh
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables scientific computing, mathematical problem solving, and step-by-step mathematical solutions through Wolfram Alpha's mobile API. Supports real-time streaming responses and multiple output formats for enhanced mathematical and scientific queries.
    1
    MIT

  • Wolfram Alpha MCP Server

    henryhawke
    F
    license
    A
    quality
    D
    maintenance
    Provides access to Wolfram Alpha's computational knowledge engine for mathematical calculations, scientific computing, data analysis, and factual information through natural language queries.
    2
    6
    -

Appeared in Searches