Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

search_by_category

Read-onlyIdempotent

List every financial metric and tool in a chosen category from Finance Toolkit, including ratios, technicals, economics, or discovery, and return names with descriptions.

Instructions

Finance Toolkit: list every metric/tool within a category of prices, financial statements, ratios and other calculations.

    Args:
        category: One of the category names returned by ``search_metric_categories``,
            e.g. ``ratios``, ``technicals``, ``economics``, ``discovery``.

    Returns:
        str: Markdown table of tool names and their descriptions for the
            requested category, or an error message if the category is unknown.

Input Schema

Name	Required	Description	Default
`category`	Yes	Category name as returned by search.categories, e.g. 'ratios', 'technicals', 'economics', 'discovery'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the output is a Markdown table and an error message is returned for an unknown category, which tells the agent how failures surface.

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?

Purpose is front-loaded in the first sentence, followed by a tidy Args/Returns block. The Returns explanation duplicates what the output schema already conveys, which is mild redundancy but not bloat.

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?

Given one parameter, full schema coverage, an output schema and strong annotations, the description covers purpose, the prerequisite for the category value, and error behavior. The only omission is explicit disambiguation from search_metrics.

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?

Schema description coverage is 100% and the single parameter is fully documented in the schema with its own examples. The description's Args section largely restates the same examples (ratios, technicals, economics, discovery) without adding format or validation nuance, so the baseline 3 applies.

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 (list) and resource (every metric/tool within a category), with scope limited to categories of prices, financial statements, ratios and other calculations. It names the sibling that produces valid category names (search_metric_categories), but does not contrast itself with search_metrics, the other plausibly overlapping sibling.

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?

Provides a clear prerequisite: the category value must be one returned by search_metric_categories, with concrete examples. It lacks an explicit when-not or a direct comparison against search_metrics, so the routing guidance is useful but not complete.

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