Skip to main content
Glama
Sign In
FinPilot AI

FinPilot AI

by ShahzaadAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

calculate_financial_ratios

Compute key financial ratios such as P/E, Debt-to-Equity, and ROE for any stock ticker to assess a company's profitability, leverage, and valuation.

Instructions

Calculate and retrieve key financial ratios like P/E, Debt-to-Equity, and ROE.

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": {
      "ticker": "<ticker>"
    },
    "name": "calculate_financial_ratios"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe stock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does not mention data sources, time periods, or any limitations. While 'calculate and retrieve' implies a read-only operation, it adds no context beyond the basic action.

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 redundant information. It efficiently conveys the core function and gives concrete examples, making it highly concise and well-structured.

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?

The tool is simple with one parameter and no output schema. The description covers the essential output (ratios) and gives examples, which is sufficient for basic understanding. However, it lacks details on return format or use context, slightly reducing completeness.

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?

The input schema fully describes the only parameter (`ticker` as stock ticker symbol), achieving 100% schema coverage. The description adds no additional meaning or format details, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Calculate and retrieve key financial ratios'. It provides specific examples (P/E, Debt-to-Equity, ROE) that distinguish it from sibling tools like get_financial_statements or run_dcf_valuation. The verb+resource combination is specific and unambiguous.

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?

The description offers no guidance on when to use this tool vs. alternatives. There is no mention of prerequisites, scenarios, or exclusion of other tools. A user would have to infer usage from the name and examples alone.

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