Skip to main content
Glama

Sparse coordinate triplets

bpj_matrix_sparse_triplets
Read-onlyIdempotent

Encode only nonzero cells as one-based row-column-value triplets and preserve grid dimensions.

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

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, closed operation. The description adds meaningful behavioral detail beyond those annotations: it specifies one-based indexing, nonzero-only encoding, and preservation of grid dimensions.

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 redundant wording. Every clause contributes to describing the transformation.

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?

The description covers the core transformation for a simple tool whose annotations carry the safety profile. However, with no output schema and the sole parameter undocumented in the schema, it should clarify the exact input format and return structure more fully.

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?

The single parameter has 0% schema description coverage, and the description only refers to 'matrix' conceptually. It does not explain that the input must be a JSON string representing a rectangular numeric matrix, nor does it add format or size guidance beyond the schema title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb, resource, and output semantics: encode only nonzero cells as one-based row-column-value triplets while preserving grid dimensions. This distinguishes it clearly from dense matrix operations in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'only nonzero cells' implies the tool is for sparse encoding, but it does not explicitly say when to choose this over dense alternatives or when not to use it. With many matrix siblings, more routing guidance would be valuable.

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.