Skip to main content
Glama

compute_pca_svd

Computes verified top-k Principal Component Analysis (PCA) / Singular Value Decomposition (SVD) on distributed GPU workers via randomized subspace iteration or stateful power iteration.

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>",
      "k": "<k>"
    },
    "name": "compute_pca_svd"
  }
}

Input Schema

NameRequiredDescriptionDefault
kYesNumber of top singular/principal components to extract.
centerNoMean-center columns before decomposition (standard PCA).
matrixYesFile path (.npy/.npz/.safetensors) or inline 2D array of shape (M, N).
methodNoDecomposition algorithm ('randomized' or 'power_iteration').randomized
output_pathNoOptional output file path (.npz or .safetensors) to save U, S, Vt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and largely drops it. It does not say whether this is a long-running/async job, what GPU resources are consumed, whether the result is returned or only written to output_path, or what 'verified' actually guarantees. Mentioning 'distributed GPU workers' and 'stateful power iteration' hints at execution characteristics but no operational consequence is spelled out.

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 repetition. It is dense with jargon ('verified', 'stateful power iteration') but every clause carries information, and 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?

For a five-parameter distributed GPU compute tool with no annotations and no output schema, the description is thin. The agent cannot tell whether the call blocks until completion, how results are delivered relative to output_path, or what failure modes exist — all of which matter for a job of this weight.

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 100%, so all five parameters are already documented, establishing a baseline of 3. The description adds only the 'top-k' framing, which is consistent with the k parameter but does not clarify format, defaults, or interaction between method and center beyond what the schema states.

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?

States a specific verb and resource: 'Computes verified top-k PCA/SVD' on 'distributed GPU workers', plus the algorithmic approach. The resource and scope are unambiguous and clearly distinct from siblings like execute_distributed_matmul or batch_similarity_search. It stops short of naming a sibling to route against, so it lands at 4 rather than 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?

The description says what the tool does but never when to choose it over alternatives or what preconditions apply. There is no guidance on when PCA/SVD is the right call, when to prefer a sibling operation, matrix size limits, or whether a prior job must have completed. The agent must infer usage from the name 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.