Skip to main content
Glama
Sign In
mcp-parigp

mcp-parigp

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

quadratic_forms

Compute reduced binary quadratic forms for a given discriminant D, where D is a nonzero integer congruent to 0 or 1 modulo 4.

Instructions

Compute reduced binary quadratic forms of discriminant D.

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": {
      "D": "<D>"
    },
    "name": "quadratic_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
DYesDiscriminant (D ≡ 0, 1 mod 4, D ≠ 0).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 must fully disclose behavior. It omits that reduced forms are typically for negative discriminants D < 0, and does not state what happens with positive D. The schema only notes D ≡ 0,1 mod 4 and D ≠ 0, missing the sign constraint.

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 concise sentence that efficiently communicates the tool's core function without any unnecessary words. However, it is slightly under-specified for the complexity of the operation.

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

Completeness3/5

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

Given the availability of an output schema and a single parameter, the description is minimally adequate. However, it lacks clarity on the mathematical context (e.g., D must be negative) and does not help the agent distinguish from closely related siblings.

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?

With 100% schema description coverage for the single parameter D, the baseline is 3. The tool description adds no further parameter guidance beyond 'compute reduced binary quadratic forms of discriminant D', which is already implied by 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 clearly states the verb 'Compute' and the resource 'reduced binary quadratic forms of discriminant D', which is specific and distinct from sibling tools like qfbclassno (class number) and qfbsolve (solve equations).

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 on when to use this tool versus alternatives such as qfbclassno, qfbsolve, or quadregulator. The description does not mention prerequisites or typical use cases, leaving the agent without selection context.

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