Skip to main content
Glama

Matrix product

bpj_matrix_multiply
Read-onlyIdempotent

Multiply conformable matrices using row-by-column dot products.

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>",
      "other": "<other>"
    },
    "name": "bpj_matrix_multiply"
  }
}

Input Schema

NameRequiredDescriptionDefault
otherYes
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value by describing the algorithm ('row-by-column dot products'), which implicitly separates it from element-wise multiplication, but it says nothing about what happens with non-conformable inputs, whether errors are raised, or how results are serialized.

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 zero filler and no redundancy. Its brevity is efficient, though it borders on under-specification rather than being genuinely concise.

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 two-parameter pure function with no output schema, the definition covers the core operation and its conformability requirement. It omits operand ordering, the fact that inputs are JSON-encoded strings rather than native arrays, and the result format, which leaves meaningful gaps for an agent constructing the call.

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 the description supplies no parameter detail at all. Critically, matrix multiplication is order-sensitive, yet the description never states that 'matrix' is the left operand and 'other' the right; the only hints come from schema titles, not the description, which fails to compensate for the coverage gap.

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 names a specific verb and resource ('Multiply ... matrices') and adds the qualifying constraint 'conformable', so the agent knows the shape requirement. It does not distinguish this from nearby siblings such as bpj_matrix_hadamard (element-wise product) or bpj_matrix_direct_sum, which are the most likely confusions.

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 named alternative. An agent choosing among matrix operations (Hadamard, direct sum, transpose) gets no routing signal from the text alone.

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.