Skip to main content
Glama

Hadamard product

bpj_matrix_hadamard
Read-onlyIdempotent

Multiply corresponding cells of equally shaped matrices.

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

Input Schema

NameRequiredDescriptionDefault
otherYes
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds one useful behavioral constraint — the operands must be equally shaped — but says nothing about what happens on shape mismatch, how errors surface, or what the result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the operation and its precondition appear in the first few words.

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 mathematically simple, annotation-covered, no-output-schema tool, this is nearly adequate. The remaining gap is the input encoding — how to express a matrix within a JSON string — plus mismatch/error behavior, which matters because both parameters are opaque strings at 0% schema coverage.

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

Parameters3/5

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

Schema description coverage is 0%, so the burden falls on the description, and it partially compensates: 'equally shaped' constrains both parameters relative to each other, and 'corresponding cells' clarifies what pairing means. However, it never explains that the inputs are JSON-serialized nested arrays (both params are strings capped at 12000 characters), leaving the actual serialization format to inference.

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 and effect, 'Multiply corresponding cells', which makes clear this is an element-wise operation rather than standard matrix multiplication. It is clear enough to separate it from a sibling like bpj_matrix_multiply, but it never names or explicitly contrasts with any alternative, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as bpj_matrix_multiply for true matrix products. The only implicit guidance is the 'equally shaped' precondition, which is a constraint rather than usage routing.

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.