Skip to main content
Glama
Sign In
NitroStack Calculator MCP Server

NitroStack Calculator MCP Server

by Tarika06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_safe_to_spend

Determine how much a user can safely spend by calculating their current safe-to-spend threshold based on financial data.

Instructions

Calculates the user's current safe-to-spend threshold.

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": {
      "user_id": "<user_id>"
    },
    "name": "get_safe_to_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description must fully convey behavioral traits. It only states 'calculates', implying a read operation, but does not disclose whether it requires authorization, is rate-limited, or has any side effects. For a non-annotated tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundancy, but it is too brief to be considered well-sized. Essential details about usage and parameters are omitted, making it concise at the cost of completeness.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description should still clarify the concept of 'safe-to-spend threshold' and any computational context. It fails to provide sufficient information for reliable agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no information about the single parameter 'user_id'. The agent receives no hints about its format, purpose, or constraints beyond the schema's type declaration.

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 uses a specific verb 'calculates' and identifies the resource 'user's current safe-to-spend threshold', clearly indicating the tool's function. It distinguishes from generic siblings like 'calculate' and 'fetch_account_summary' via the specific concept of safe-to-spend. However, it does not define what 'safe-to-spend' means, which could be ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. Siblings like 'fetch_account_summary' or 'compute_financial_dna_score' might overlap, but the description offers no exclusion criteria or context for selection.

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