Skip to main content
Glama
Sign In
mcp-parigp

mcp-parigp

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

euler

Compute Euler's constant (gamma) with adjustable precision up to specified bits.

Instructions

Get Euler's constant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "euler"
  }
}

Input Schema

NameRequiredDescriptionDefault
precisionNoOptional precision in bits.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It fails to mention what the tool returns, default behavior for precision, or side effects. The single line is insufficient for an agent to understand the tool's behavior beyond its core function.

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 extremely concise at only two words. However, it is arguably too minimal; while front-loaded and lacking waste, it could provide slightly more context without harming conciseness. Still, it earns a 4 for avoiding unnecessary content.

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 (1 optional parameter, no annotations), the description should at least hint at the precision parameter's effect or mention the return type. The existence of an output schema reduces the burden for return value explanation, but overall context remains incomplete.

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% as the only parameter 'precision' is described in the schema. The description adds nothing beyond the schema, so baseline score of 3 is appropriate according to guidelines.

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 'Get Euler's constant' clearly states the verb and resource, making the purpose unambiguous. It effectively distinguishes from sibling tools like 'pi' or 'Catalan' by specifying which mathematical constant is being retrieved.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it explain any context or prerequisites. The agent receives no help in deciding between euler and other constant retrieval tools or understanding the optional precision parameter.

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