Skip to main content
Glama

distribution_probability

Calculate the probability that a random variable X meets a condition (e.g., X < 5) for a specified distribution type and parameters, returning symbolic or numeric results.

Instructions

    Calculate probability P(condition).

    ═══════════════════════════════════════════════════════════════════════
    🆕 NOT AVAILABLE IN SYMPY-MCP!
    ═══════════════════════════════════════════════════════════════════════

    Args:
        distribution_type: Type of distribution
        parameters: Distribution parameters
        condition: Condition string using X as the random variable
            - "X < 5", "X > 2", "X >= 3", "X <= 1"
            - "2 < X < 5" (between two values)

    Returns:
        Probability (symbolic or numeric)

    Examples:
        # P(X < 0) for standard normal
        distribution_probability("normal", {"mean": "0", "std": "1"}, "X < 0")
        → {"probability": "1/2", ...}

        # P(1 < X < 3) for exponential
        distribution_probability("exponential", {"rate": "lambda"}, "1 < X < 3")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conditionYes
parametersYes
distribution_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description discloses the return type (symbolic or numeric) and condition syntax, adding some behavioral context beyond the empty annotations. However, it does not state whether a distribution must be defined first, what happens with invalid conditions, or other side effects/constraints. The 'NOT AVAILABLE' banner is ambiguous.

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

Conciseness3/5

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

The description is structured with Args/Returns/Examples, but includes a large decorative warning banner that adds no operational value and occupies space. The warning is not front-loaded critical info, making the description less concise than it could be.

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

Completeness4/5

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

The description covers the core behavior: input format, output type, and examples, which is mostly sufficient for a probability calculator. However, with no annotations and an empty schema, edge cases, setup requirements, and error behavior are omitted, leaving minor gaps.

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 input schema has no descriptions for any parameter (0% coverage). The description fully compensates by explaining distribution_type, parameters as a dictionary, and condition with explicit string format and multiple examples, adding meaningful semantics beyond the 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 opens with 'Calculate probability P(condition)' and provides distribution_types and condition examples. This clearly specifies the verb (calculate) and resource (probability for a distribution), distinguishing it from siblings like distribution_stats or define_distribution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Examples imply usage but no explicit when-to-use guidance or alternatives are given. The warning 'NOT AVAILABLE IN SYMPY-MCP!' is a limitation note but does not clarify when to choose this tool over others. No prerequisites or exclusions are mentioned.

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