Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Screen Mutual Funds

screen_mutual_funds
Read-onlyIdempotent

Rank, filter or compare Indian mutual funds: one row per fund with category, benchmark, 1/3/5y returns vs benchmark, base expense ratio (and all-in), average AUM, first NAV date. Filter and sort by those, or compare up to 10 scheme_codes. One category adds its quartiles. Past returns, not 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": "screen_mutual_funds"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoDefault direct.
sortNo
limitNoDefault 20.
orderNo
cursorNoA previous page's next_cursor.
categoryNoKey or name, e.g. "flexi-cap", "Liquid"; unknown lists all.
benchmarkNoe.g. "Nifty 50 TRI".
fund_houseNoe.g. "HDFC Mutual Fund".
first_nav_toNo
scheme_codesNoPlans to compare, alone.
first_nav_fromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedInput schema / properties / category / description
      Previous value: -"e.g. \"flexi-cap\", \"liquid\"; unknown lists all."New value: +"Key or name, e.g. \"flexi-cap\", \"Liquid\"; unknown lists all."
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "A previous page's next_cursor.",
      +  "maxLength": 400,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds real value on top: the per-row output contract, the quartile side effect for a single category, the "past returns, not advice" caveat, and that an unknown category falls back to listing all. Pagination/cursor behavior is left entirely to the schema, so it is not complete.

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?

Three tight sentences with the row contract front-loaded, then query modes, then the caveat. No filler or repetition; every clause carries information about either output or behavior.

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 an 11-parameter screening tool with no output schema, describing the returned columns is the right compensation and it is done well. Remaining gaps are modest: cursor-based pagination and what "quartiles" concretely return are not explained.

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?

With 73% schema description coverage the schema already documents plan, limit, category, benchmark, fund_house and scheme_codes. The description's "filter and sort by those" usefully signals which row fields are queryable, but its statements about limits and scheme_codes largely restate the schema's maxItems and default values, adding little new meaning.

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?

"Rank, filter or compare Indian mutual funds" gives a specific verb set plus the resource, and immediately defines the shape of a result row (category, benchmark, 1/3/5y returns, expense ratio, AUM, first NAV date). This distinguishes it from the single-fund siblings such as get_mutual_fund and get_mutual_fund_nav_history.

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?

The description states the three modes (rank, filter, compare) and the guardrail that scheme_codes is used "alone" for comparison, plus that a single category unlocks quartiles. It does not explicitly say when to prefer this over get_mutual_fund or get_mutual_fund_nav_history, so the routing guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.