Skip to main content
Glama

Matrix norm comparison

bpj_matrix_norms
Read-onlyIdempotent

Compare the induced one-norm and infinity-norm with the Frobenius norm.

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

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds nothing beyond the mathematical intent: it does not say how large a matrix is practical, what happens with non-rectangular or malformed input, or whether the norms are returned as raw values or as a comparative summary.

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 or redundancy. It is efficient, though its brevity is partly the source of the specification gaps noted elsewhere rather than deliberate economy.

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 bears responsibility for describing the return value, and it does not. Combined with the undocumented matrix format and the unspecified interpretation of 'compare', an agent would have to guess on both the input and output side of the call.

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?

There is one required parameter with 0% schema description coverage, and the description says nothing about it. The only clue is the schema's own title, 'Rectangular numeric matrix (JSON)', which leaves the encoding (nested arrays? flat list with dimensions?) undefined for a maxLength-12000 string; the description does not compensate for this gap at all.

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 gives a specific verb ('Compare') and specific mathematical objects (induced one-norm, infinity-norm, Frobenius norm), which clearly separates it from siblings like bpj_matrix_determinant or bpj_matrix_trace. However, it never says what a 'comparison' produces (three numeric values? a relationship? an ordering?), so the resource is precise but the outcome is not.

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 choose this tool versus the many other matrix-analysis siblings, and no prerequisites or exclusions are stated. The agent can infer it is a norm tool, but nothing tells it why to pick this over, say, a trace or symmetry check.

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.