Skip to main content
Glama
Sign In

Scientific Calculator

by ai.saifs
OverviewDiscussionsAdmin

Dot Product

calculator_dot
Read-only

Dot product of two equal-length vectors.

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": {
      "vector_a": "<vector_a>",
      "vector_b": "<vector_b>"
    },
    "name": "calculator_dot"
  }
}

Input Schema

NameRequiredDescriptionDefault
vector_aYesFirst vector.
vector_bYesSecond vector.

Output Schema

NameRequiredDescriptionDefault
resultYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds the useful input constraint that vectors must be equal-length, but does not explain behavior for mismatched lengths or other edge cases.

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?

The description is a single front-loaded sentence with no wasted words. It immediately states the operation and the core input constraint.

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?

For a simple pure math operation, with an output schema present and annotations covering safety, the description is nearly complete. The main minor gap is not stating how unequal-length vectors are handled.

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 the schema already documents both vector parameters with examples. The description adds the equal-length constraint, which is meaningful beyond the schema, but does not add further parameter details.

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 states a specific mathematical operation (dot product) applied to a specific resource (two equal-length vectors). It is clear but does not explicitly distinguish itself from siblings such as calculator_cross or calculator_vector.

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 guidance on when to use this tool versus alternatives like calculator_cross, calculator_vector, or calculator_magnitude. The operation is mathematically implied, but no selection context or exclusions are provided.

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

All Scientific Calculator toolsInspect
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.

Resources