Skip to main content
Glama

sigmoid_calculate

Read-onlyIdempotent

Calculate sigmoid, tanh, relu, leaky_relu, elu, or swish activation values and derivatives from an input number for neural network workflows.

Instructions

Compute activation functions (sigmoid, tanh, relu, leaky_relu, elu, swish) and their derivatives.

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": {
      "x": "<x>"
    },
    "name": "sigmoid_calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesInput value.
functionNoActivation function: sigmoid, tanh, relu, leaky_relu, elu, or swish. Default: sigmoid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds the supported-function inventory, which is useful, but says nothing about domain behavior (e.g. saturation behavior, what happens with out-of-range inputs). It also mentions 'derivatives' without explaining how to obtain one, which leaves a behavioral gap.

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 well-formed sentence with the function inventory up front and no filler. The trailing phrase 'and their derivatives' is the one element that is not earned, since the schema provides no way to request a derivative.

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 simple two-parameter numeric tool with no output schema, the description is nearly sufficient, but the derivative claim is unsupported by the schema and could mislead an agent into hunting for a missing parameter. Otherwise nothing critical is missing.

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% and the schema already lists the six function names plus the sigmoid default, so the description is largely redundant here. The mention of 'derivatives' does not map to any parameter in the schema, adding ambiguity rather than clarity.

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 ('Compute') and resource (activation functions), and enumerates the supported function names, so an agent knows exactly what it produces. It does not differentiate from neighboring math tools such as newton_math or numerical_diff, which is the only thing keeping it below 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 statement of when to pick this over alternatives (e.g. numerical_diff for derivatives) and no preconditions or exclusions. The reader must infer usage purely from the name and function list.

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

Deploy Server

Other Tools