Aman-Amith-Shastry-scientific_computation_mcp

vector_project

Read-onlyIdempotent

    Projects a stored vector onto another vector.

    Args:
        name (str): Name of the stored vector to project.
        new_vector (list[float]): The vector to project onto.

    Returns:
        Tensor: The projection result vector.

    Raises:
        ValueError: If the vector name is not found or projection fails.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Name of the stored vector to project.
`new_vector`	Yes	The vector to project onto, as a flat list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

addedInput schema / properties / name / description

Added value: +"Name of the stored vector to project."

addedInput schema / properties / new_vector / description

Added value: +"The vector to project onto, as a flat list."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        {
+          "items": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          },
+          "type": "array"
+        },
+        {
+          "items": {
+            "items": {
+              "items": {
+                "type": "number"
+              },
+              "type": "array"
+            },
+            "type": "array"
+          },
+          "type": "array"
+        }
+      ],
+      "title": "Result"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "vector_projectOutput",
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds value by specifying error behavior (ValueError if name not found or projection fails) and the return type (Tensor), which goes beyond the structured annotations.

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?

The description is a single concise sentence plus a structured Args/Returns/Raises block. It is front-loaded with the main purpose and avoids unnecessary elaboration. However, the Args block largely duplicates the schema, making it slightly redundant, but overall it remains tight and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, and the description, combined with the output schema, provides sufficient information for an agent to call it correctly. It covers the main inputs, the return type, and an error condition. While it does not mention dimension matching or prerequisites for the stored vector, such details are likely implied and not critical for a straightforward projection operation.

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 both parameters are already documented in the schema. The description's Args section repeats the schema text ('Name of the stored vector to project' and 'The vector to project onto, as a flat list') without adding new semantic details such as vector dimension requirements or format expectations. Thus it adds no significant value beyond the schema.

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 action: 'Projects a stored vector onto another vector.' It clearly identifies the resource (stored vector) and the operation (projection), which distinguishes it from sibling operations like add, multiply, or determinant.

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 description explains what the tool does but does not provide explicit guidance on when to use it versus alternatives. It neither names sibling tools nor gives conditions for selection. The usage context is implied by the operation but not clarified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aman-Amith-Shastry-scientific_computation_mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.