Skip to main content
Glama

Transpose a numeric matrix

bpj_matrix_transpose
Read-onlyIdempotent

Swap the row and column axes of a rectangular numeric grid.

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_transpose"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 a closed world, so the safety profile is fully covered. The description adds only the implicit constraint that input must be rectangular (ragged rows presumably fail), but says nothing about error behavior, output encoding, or size limits. With annotations doing the heavy lifting, a 3 is fitting.

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 short, front-loaded sentence with no filler. It is efficient, though its brevity means it fails to carry the input-format detail the schema omits.

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 0% schema description coverage, the description should explain the input encoding and what comes back (a transposed grid, presumably in the same string format). Neither is addressed, so an agent must guess how to serialize the matrix and what to expect in the response.

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

Parameters1/5

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

Schema description coverage is 0%, and the single parameter is a string containing JSON (maxLength 12000) — the description never says the matrix must be supplied as a JSON-encoded string rather than a native array. 'Rectangular numeric grid' gives a hint about shape but leaves the wire format and element constraints undocumented, which is exactly the gap the description needed to close.

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 ('Swap') and the exact transformation applied to the two axes of a rectangular numeric grid, so the operation is unambiguous. It does not differentiate itself from the many other matrix siblings, but the purpose itself is fully legible.

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?

No when-to-use or when-not guidance at all, and the dense matrix sibling set (multiply, rref, determinant, trace, etc.) makes selection non-trivial. The agent must infer from the name alone that this is the tool for axis reorientation.

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.