Fortunest demo

Warnings

warnings

Read-onlyIdempotent

DEMO portfolio (synthetic, shared, read-only). Read the portfolio's data-quality warnings — what the import could not read, what it assumed, and what could not be priced — instead of the whole context. Each item carries the engine's own sentence verbatim plus its kind, the account that raised it and the symbols it names. kind filters to one of: parse, unpriced, fx, delisted, openingCash, shortCredit, openingBalance, writeOff, skippedRows, exportWindow, missingHistory, other. symbol filters to the warnings naming that holding. byKind counts the FULL list, not the filtered page, so one call shows what else exists. Paginate with limit/offset and nextOffset. These are import and valuation caveats, never investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "warnings"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No
`limit`	No
`offset`	No
`symbol`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description adds meaningful context beyond them: item shape (verbatim engine sentence, kind, raising account, named symbols), the fact that byKind counts the full list while items are paginated, and the caveat that these are import/valuation notes and not investment advice.

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

Conciseness4/5

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

It is a single dense block, but the key scoping statement ('instead of the whole context') is front-loaded and each following sentence adds distinct information about filters, pagination, or item contents. The long inline enum list makes it heavier to read than necessary.

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?

With no output schema, the description fully covers what is needed: what an item contains, how filtering and counting behave differently, how to paginate with nextOffset, and the semantic status of the data. Nothing required to call it correctly is missing.

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

Parameters4/5

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

With 0% schema description coverage, the description must carry parameter meaning and largely does: kind is described as a single-kind filter (repeating the enum labels), symbol as 'the warnings naming that holding', and limit/offset as pagination paired with nextOffset. It omits defaults and the limit 50 / offset 500 ceilings present in the schema, leaving a small 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?

States a specific verb and resource ('Read the portfolio's data-quality warnings') and enumerates the three content categories: what the import could not read, what it assumed, and what could not be priced. It also differentiates scope from the broader context tool ('instead of the whole context'), so an agent can tell it apart from get_core without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear selection context: use this when you need the caveats rather than the whole portfolio context, and use byKind to see what exists beyond the current filtered page. It stops short of naming a specific sibling tool as the alternative, so routing is implied rather than explicit.

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

All Fortunest demo tools Inspect

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.