Skip to main content
Glama
Sign In
NitroStack Calculator MCP Server

NitroStack Calculator MCP Server

by Tarika06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

compute_financial_dna_score

Computes a financial health score using six dimensions: emergency fund, insurance, investments, debt, tax, and retirement.

Instructions

Runs the deterministic 6-dimension health score.

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": "compute_financial_dna_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
dimensionsNoOptional subset; omit to recompute all six

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'deterministic' but does not disclose side effects (e.g., reads/writes), authentication needs, or output behavior. For a compute tool, transparency is minimal.

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, which is concise but lacks structure. It front-loads the key concept ('health score') but fails to elaborate with a second sentence about dimensions or context.

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 no output schema and no annotations, the description is incomplete for a tool with 2 parameters and a complex concept (6-dimension score). It does not hint at return format, use of dimensions, or what 'deterministic' implies operationally.

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 coverage is 50%: 'dimensions' has a description in schema, but 'user_id' lacks description. The tool description does not add meaning beyond the schema. At 50% coverage, the description should compensate but doesn't explain the role of user_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Runs the deterministic 6-dimension health score' indicates the tool produces a health score, but 'runs' is vague and doesn't specify the resource (user) or the nature of the score. It distinguishes from siblings like 'calculate' only by mentioning '6-dimension', but purpose is incomplete.

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 on when to use this tool versus alternatives like 'calculate' or 'get_safe_to_spend'. No exclusions or context provided. The description leaves the agent without any usage direction.

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