Skip to main content
Glama

Integer square root and remainder

bpj_discrete_integer_square_root
Read-onlyIdempotent

Find the exact floor square root of a nonnegative decimal integer and its remainder.

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": {
      "value": "<value>"
    },
    "name": "bpj_discrete_integer_square_root"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is fully covered. The description adds genuine behavioral content by specifying 'exact floor' (truncation, not rounding) and constraining input to nonnegative decimals, but says nothing about failure on negative input or about the shape of the returned root and remainder.

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 filler; every clause carries meaning (exactness, floor semantics, input domain, and the two returned quantities).

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 one-parameter pure computation, the description does name both outputs and pins the input domain, which is close to sufficient. However, with no output schema and no description of return types or negative-input behavior, an agent still has to discover the response shape empirically.

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 0%, so the single 'value' parameter relies entirely on its title. The description reinforces the domain ('nonnegative decimal integer'), which clarifies that it is a string-encoded decimal rather than a number, but it omits the maxLength=100 bound and any format notes.

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 ('find') and a precise resource pair ('exact floor square root' plus 'remainder') over a defined input domain ('nonnegative decimal integer'). This is unambiguous versus siblings such as bpj_series_root_mean_square or bpj_discrete_continued_fraction, though it never names or contrasts an alternative explicitly.

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 when-to-use, when-not-to-use, or alternative tool guidance. The operation is self-evident enough that an agent can infer the use case, but that inference comes from the tool name rather than the description.

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.