Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

search_metrics

Read-onlyIdempotent

Search financial metrics by keyword to find relevant calculation tools, with typo tolerance and support for common financial abbreviations.

Instructions

Finance Toolkit: search the metrics this server calculates (prices, financial statements, ratios and more) by keyword, with typo tolerance.

    Supports minor typos and common financial abbreviations. Tokens
    shorter than four characters bypass fuzzy matching and require an
    exact substring hit.

    Args:
        query: Free-text search string, e.g. ``'debt'``,
            ``'moving average'``, ``'sharpe'``, or ``'retun on equty'``.

    Returns:
        str: Markdown table of matching tools sorted by relevance score,
            or a guidance message when no strong matches are found.

Input Schema

Name	Required	Description	Default
`query`	Yes	Free-text keyword to search across all metric names and descriptions, e.g. 'sharpe', 'debt', or 'moving average'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the bar is lowered, and the description still adds real behavioral detail: fuzzy matching on multi-character tokens, exact-substring requirement for tokens under four characters, and relevance-sorted output with a fallback guidance message. It does not disclose result limits or pagination, which would have earned a 5.

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?

Well front-loaded: the core capability and the typo-tolerance rule appear before the Args/Returns scaffolding. The 'Finance Toolkit:' prefix and docstring-style block add slight padding but nothing is genuinely wasted.

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?

For a single-parameter search tool with an output schema, the description covers input intent, matching semantics, and fallback behavior. The only meaningful omission is that it never distinguishes itself from the sibling category search tools an agent will see listed alongside it.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema by supplying multiple worked examples including a deliberately misspelled 'retun on equty' that concretely demonstrates the typo-tolerance contract for the query parameter.

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

Purpose4/5

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

States a specific verb and resource ('search the metrics this server calculates') and scopes the domain with concrete examples (prices, financial statements, ratios). It is clearly distinguishable from the category-oriented siblings, though it does not explicitly name search_metric_categories or search_by_category to reinforce the distinction.

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

Usage Guidelines3/5

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

Usage is implied (use when you want to find a metric by keyword, typos tolerated), but there is no explicit when-not or routing guidance against the very similar sibling tools search_metric_categories and search_by_category. An agent must infer which of the three search entry points to pick.

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