Skip to main content
Glama
Sign In
mcp-parigp

mcp-parigp

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

bnrinit

Initialize a ray number field for computing ray class groups. Provide a base number field and a modulus to define the ray class group.

Instructions

Initialize a ray number field (class field).

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": {
      "nf": "<nf>",
      "modulus": "<modulus>"
    },
    "name": "bnrinit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nfYesNumber field from nfinit.
signNo1 for full, -1 for real.
modulusYesModulus for ray class group.

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?

No annotations provided, and the description fails to disclose any behavioral traits such as side effects, required permissions, or error conditions. The tool likely creates an object, but the description does not clarify mutability or state changes.

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?

Description is extremely concise at one sentence. It is front-loaded but may be overly terse; additional detail could be added without significant length increase.

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?

No output schema exists, and the description does not explain what the tool returns. For a complex number theory tool, this omission leaves an agent without essential context for further processing.

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?

Input schema covers all parameters with descriptions (100% coverage), so baseline is 3. The description adds no additional semantic information beyond what the schema provides, such as the relationship between nf and modulus or the meaning of sign.

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?

Description states 'Initialize a ray number field (class field)', which clearly indicates verb and resource. However, it does not differentiate from sibling tools like bnfinit (which initializes a number field) or bnrL1, leaving ambiguity about the specific purpose.

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 bnrL1 or bnfinit. There is no mention of prerequisites, such as the need for a previously initialized number field via nfinit, or when not to use it.

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