Skip to main content
Glama

Solve a small linear system

bpj_matrix_linear_system
Read-onlyIdempotent

Solve a square nonsingular system of up to twelve equations with partial pivoting.

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>",
      "rhs": "<rhs>"
    },
    "name": "bpj_matrix_linear_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
rhsYes
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds the algorithmic detail of partial pivoting and a size limit, which is useful numeric context, but it says nothing about error behavior for singular input or the shape of the returned solution.

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?

A single front-loaded sentence with no filler, and the constraints appear before the algorithmic detail. It is efficient, though arguably too terse given the encoding ambiguity of the two string parameters.

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 schema description coverage, the description must carry more of the load than it does: the required JSON string encoding of matrix and rhs, the expected return form, and the singular-matrix failure mode are all unspecified. For a numerical solver taking 12000-character string payloads, this leaves real invocation risk.

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?

Schema description coverage is 0% and both parameters are typed as strings up to 12000 characters, so the critical question of how to encode the matrix (JSON array, row-major nesting, orientation) and the rhs vector is left entirely unaddressed. The only implicit parameter link is that the matrix must be square with at most twelve rows.

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 uses a specific verb ('solve') plus a precisely bounded resource ('square nonsingular system of up to twelve equations') and even names the algorithm ('partial pivoting'). It is clearly distinguishable from matrix siblings like transpose, rref, or determinant, though it does not explicitly name them.

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?

The 'square nonsingular' and 'up to twelve equations' phrasing implicitly defines the valid input domain, which functions as a precondition. However, there is no explicit guidance on when to choose this over related tools such as bpj_matrix_rref or bpj_matrix_determinant, and no note on what to do for singular or larger systems.

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.