Skip to main content
Glama
Sign In
mcp-parigp

mcp-parigp

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

ellwp

Compute the Weierstrass p-function for an elliptic curve with customizable number of terms and flags.

Instructions

Compute the Weierstrass p-function.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "E": "<E>"
    },
    "name": "ellwp"
  }
}

Input Schema

NameRequiredDescriptionDefault
EYesElliptic curve structure.
nNoNumber of terms (default 6).
flagsNoComputation flags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits, but it only states the computation. It does not mention output format, special cases (e.g., singular curves), or any side effects, leaving significant ambiguity.

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 a single, efficient sentence. It is well-structured and on-topic, though slightly more context could be included without becoming verbose.

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 mathematical complexity and the presence of many sibling elliptic functions, the description is insufficient. It lacks context about the tool's role in number theory or relationship to other tools, making it incomplete for an agent to select correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The tool's description adds no extra parameter meaning; the schema already describes each parameter. Thus, no additional value is provided.

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 uses a specific verb ('Compute') and identifies the resource ('Weierstrass p-function'), clearly indicating the tool's purpose. However, it does not differentiate from sibling elliptic curve functions like ellzeta or ellj, which are also specific.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description lacks context on prerequisites or scenarios, leaving the agent to infer usage from the name alone.

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

Deploy Server

Other Tools