Skip to main content
Glama

Two-decimal amount precision check

bpj_dq_two_decimal_money
Read-onlyIdempotent

Flag amounts whose plain decimal representation needs more than two fraction digits.

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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_dq_two_decimal_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile needs no restating. The description adds the flagging rule but leaves behavior unclear for edge cases implied by 'plain decimal representation' — trailing zeros, exponent notation, currency symbols, nulls — and says nothing about what a flagged result contains.

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 the rule stated immediately and no filler or redundant restatement of the title. Nothing can be trimmed without losing the criterion itself.

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?

With no output schema and zero parameter documentation, the description is the only source of contract detail, and it supplies just the flagging rule. For a check tool an agent must call with a JSON record array and a column name, the input format and the shape of flagged results are both missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both required parameters have 0% schema description coverage beyond bare titles ('Record array (JSON)', 'Column name'), so the description carries the full burden — and it mentions neither parameter. It never explains the expected JSON shape of 'rows' or that 'column' must name a field within that array, leaving an agent to guess the calling convention.

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?

States a specific verb ('Flag') plus a precise predicate (amounts whose plain decimal representation needs more than two fraction digits), which clearly separates it from neighboring numeric checks like whole-number or numeric-range checks. It never names a sibling, so an agent must infer the boundary from the predicate alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the domain: apply it to money/amount columns when validating scale. There is no explicit when-to-use statement and no guidance on when a different numeric check (whole numbers, numeric type, numeric range) is the right pick instead, nor on what happens with non-numeric or empty cells.

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.