Skip to main content
Glama

Count integer partitions

bpj_discrete_integer_partitions
Read-onlyIdempotent

Count additive partitions of a nonnegative integer without distinguishing term order.

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": "bpj_discrete_integer_partitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the precise computation semantics (unordered additive partitions), but says nothing about the result being a single large integer, the rapid growth of partition counts at the maximum n=150, or any overflow behavior.

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?

A single front-loaded sentence with no redundant wording; the disambiguating clause is placed where it matters immediately after the core definition. Nothing in it could be removed without losing meaning.

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

Completeness4/5

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

For a one-parameter pure computation with full annotations, the definition covers what is computed and the input domain. The main remaining gap is that no output schema exists and the description never states the return shape (a count as an integer), though the verb 'Count' strongly implies it.

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 coverage is 0%, but there is only one parameter and the schema itself carries the constraints (minimum 0, maximum 150, title 'Nonnegative integer'). The description reinforces that n is a nonnegative integer being partitioned but adds no format, boundary, or representational detail beyond the schema's own constraints.

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 gives a specific verb ('Count') and resource ('additive partitions of a nonnegative integer'), and adds the key disambiguator 'without distinguishing term order', which separates it from order-sensitive variants such as compositions. It does not name any sibling tool explicitly, so it stops short of a 5.

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 tool versus any alternative, no mention of when it is not appropriate, and no prerequisites or context. The agent must infer the use case entirely from the mathematical phrasing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.