Skip to main content
Glama

Square matrix determinant

bpj_matrix_determinant
Read-onlyIdempotent

Compute a numerical determinant using partial pivoting for a square matrix of order up to twelve.

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": {
      "matrix": "<matrix>"
    },
    "name": "bpj_matrix_determinant"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely extra behavior: the numerical method (partial pivoting, implying stability) and a hard order limit of twelve. It stops short of saying what happens on a non-square or singular input or what precision to expect.

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?

One front-loaded sentence with no filler; the size limit is placed where it matters. It is lean to the point of omitting the square/JSON format detail an agent needs, but nothing in it is redundant.

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 single-parameter numeric tool with no output schema, the essentials (square requirement, order cap, method) are present, but the return value type and the string-encoded matrix format are left unstated, which is the main practical gap.

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%, so the description must carry the parameter burden. It does add the key constraint that the matrix must be square with order <= 12 (the schema title confusingly says 'Rectangular numeric matrix'), but it never specifies the JSON encoding of the string (nested arrays vs. flat list) or how malformed input is handled.

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 ('Compute'), resource ('determinant'), and even the algorithm ('partial pivoting') plus the domain limit ('square matrix of order up to twelve'). An agent can distinguish it from siblings like bpj_matrix_trace or bpj_matrix_rref without opening the schema, though it never names an alternative.

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 or when-not-to-use guidance and no mention of alternatives such as bpj_matrix_rref (which would also reveal singularity). The purpose implies usage, but nothing tells the agent how to choose among the many matrix siblings.

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.