ROIC.ai Financial Data MCP Server

Official

by roicai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

Get Latest Stock Price

get_latest_stock_price

Read-only

Fetch the current stock price for any public company by entering its ticker symbol, CIK, CUSIP, or ISIN.

Instructions

Get the most recent stock price for a company.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_latest_stock_price"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes	Company identifier: ticker symbol (e.g. AAPL), CIK, CUSIP, or ISIN

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context (e.g., data delay, market status), but it does not contradict the annotations.

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 sentence with no filler, directly stating the operation. It is appropriately sized for a simple one-parameter read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, the fully documented parameter, and the provided annotations, the description sufficiently covers what the tool does and how to invoke it. No output schema exists, but the return value is self-evident from the tool's name.

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 documents the 'identifier' parameter with supported formats (ticker, CIK, CUSIP, ISIN) and an example, achieving 100% schema coverage. The description adds nothing beyond the schema, so a baseline 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 uses a specific verb ('Get') and resource ('most recent stock price'), clearly stating the tool's purpose. The qualifier 'most recent' distinguishes it from the sibling tool 'get_stock_prices', which implies historical price data.

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 like 'get_stock_prices' or 'get_company_profile'. The description simply states the action without contextual cues or exclusions.

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