calculate_npv
Calculate Net Present Value. rate: discount rate as decimal (e.g. 0.1 = 10%). Returns: {npv, rate_percent, cashflows_count}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rate | Yes | ||
| cashflows | Yes |
Data Compute Stats Mcp
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description describes the return shape and rate format. Implies a read-only calculation; no side effects discussed but sufficient for the operation.
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?
Two sentences, front-loaded with purpose. No unnecessary words.
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?
Simple tool, but missing description for cashflows parameter and no example or edge cases. Output shape is given, but parameter documentation is incomplete.
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?
Only 'rate' is explained with format and example; 'cashflows' remains undocumented. With 0% schema coverage, description partly compensates but leaves a gap.
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?
Clearly states 'Calculate Net Present Value' as a specific verb+resource. Distinguishes from siblings like calculate_irr by focusing on NPV directly.
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 vs calculate_irr or others. The description does not mention alternatives or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.