Skip to main content
Glama

Matrix symmetry residual

bpj_matrix_symmetry
Read-onlyIdempotent

Measure the maximum absolute discrepancy between mirrored entries of a square 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_symmetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the actual computation (max absolute difference of mirrored entries), but says nothing about what happens with non-square input, how the matrix is parsed from the JSON string, or what the result looks like. Given the annotation coverage, this is adequate but thin.

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?

It is a single front-loaded sentence with no filler, and the key concept (maximum absolute mirrored discrepancy) comes first. It is perhaps too terse for a tool whose input format is undocumented, but nothing is wasted.

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, the description should clarify the return value, but it only implies a scalar without saying so. The square-versus-rectangular conflict and the total absence of JSON-input guidance leave an agent with real risk of calling it incorrectly.

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?

There is a single parameter with 0% schema description coverage, so the description must carry the burden. Instead of clarifying the expected JSON encoding (e.g. [[1,2],[3,4]]), it introduces a conflicting constraint by calling the input a 'square grid' while the schema titles it 'Rectangular numeric matrix'.

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 states a specific verb ('Measure') and precisely names the computed quantity — the maximum absolute discrepancy between mirrored entries — which distinguishes it from siblings like bpj_matrix_trace or bpj_matrix_norms. The only blemish is that it says 'square grid' while the parameter is described as a 'Rectangular numeric matrix', leaving the exact input requirement ambiguous.

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 guidance on when to use this tool versus alternatives such as bpj_matrix_norms or bpj_pairs_residual_diagnostics, and no preconditions or exclusions are stated. The agent must infer the use case purely from the mathematical quantity named.

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.