Skip to main content
Glama

catalan_calc

Read-onlyIdempotent

Calculate the nth Catalan number or generate the full sequence from 0 to n, including combinatorial interpretations for mathematical and algorithmic use cases.

Instructions

Compute the nth Catalan number and its combinatorial interpretations.

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": {
      "n": "<n>"
    },
    "name": "catalan_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYesNon-negative integer index
countNoLimit sequence length (used with sequence: true)
sequenceNoReturn the full sequence from 0 to n (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds nothing about what 'combinatorial interpretations' means in the response, and does not reconcile the odd openWorldHint=true on what should be a purely computational, closed-world tool.

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

Conciseness5/5

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

One front-loaded sentence with no filler; the operation and its subject are stated first. Nothing could be removed without losing meaning.

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?

For a three-parameter tool with no output schema, the description should clarify the relationship between n, sequence and count and what the interpretations portion returns. The safety annotations cover the operation profile, but the result shape remains unexplained.

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 n, count and sequence are already documented in the schema. The description adds no extra semantics beyond restating the computation, which is acceptable at baseline but offers no lift.

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 states a specific verb (Compute) and resource (the nth Catalan number), which lets an agent locate it unambiguously among the math siblings. The trailing phrase 'and its combinatorial interpretations' is vague and doesn't tell the agent what that portion of the output actually is.

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?

There is no guidance on when to use this versus alternatives such as pascaltri_generate or fibonacci_sequence, nor when to set sequence:true versus relying on a single value. The agent must infer the sequence/count interaction entirely from the schema.

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