Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Mutual Fund Portfolio

get_mutual_fund_portfolio
Read-onlyIdempotent

A fund's month-end portfolio: every line, largest value (INR crore) first, as compact rows (weight, ISIN, symbol, standard and printed industry or rating, rating agency, cash kind, yield/coupon/maturity) paged by offset; net assets; a summary (asset classes, cash, top 10, industries, market-cap split); debt YTM, durations, average maturity. Start year varies by house. By scheme_code, or a fund's name: its linked portfolio (link says confirmed or inferred). Else name words match statements, each at its newest in 13 months; several list house and portfolio_code. compare: bought and sold since a month. stock: funds holding a stock, with scheme codes.

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": "get_mutual_fund_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoRows per page (default 25; compare/stock max 100).
fundNoScheme name words, e.g. "parag flexi cap".
houseNoFund-house key from a previous match, e.g. "ppfas".
monthNoYYYY-MM. Default: the newest month linked to the fund.
stockNoSymbol or ISIN: funds holding it.
offsetNoA previous page's next_offset.
compareNo"previous" or YYYY-MM: changes since then.
scheme_codeNoScheme code of any plan of the fund, e.g. "122639".
statement_keyNoA previous page's statement_key.
portfolio_codeNoPortfolio code from a previous match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / statement_key
      Added value: +{
      +  "description": "A previous page's statement_key.",
      +  "maxLength": 16,
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "A previous page's next_offset.",
      +  "maximum": 100000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / top / description
      Previous value: -"Rows to list (default 25)."New value: +"Rows per page (default 25; compare/stock max 100)."
    • changedInput schema / properties / top / maximum
      Previous value: -100New value: +500
  3. Changed1 schema field changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  4. Changed3 schema fields changed
    • addedInput schema / properties / compare
      Added value: +{
      +  "description": "\"previous\" or YYYY-MM: changes since then.",
      +  "pattern": "^(previous|\\d{4}-\\d{2})$",
      +  "type": "string"
      +}
    • addedInput schema / properties / stock
      Added value: +{
      +  "description": "Symbol or ISIN: funds holding it.",
      +  "maxLength": 40,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / top / description
      Previous value: -"Holdings to list (default 25)."New value: +"Rows to list (default 25)."
  5. Changed1 schema field changed
    • changedInput schema / properties / month / description
      Previous value: -"YYYY-MM. Default: the latest month."New value: +"YYYY-MM. Default: the newest month linked to the fund."
  6. Changed1 schema field changed
    • addedInput schema / properties / scheme_code
      Added value: +{
      +  "description": "Scheme code of any plan of the fund, e.g. \"122639\".",
      +  "pattern": "^[1-9]\\d{0,8}$",
      +  "type": "string"
      +}
  7. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully adds offset paging, value-descending ordering, the confirmed-vs-inferred `link` status, the 'start year varies by house' caveat and the 13-month match window. It stops short of saying what happens on zero matches or how ambiguity resolution behaves beyond listing house and portfolio_code.

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?

Front-loaded with the primary payload and roughly a hundred words for ten parameters plus three modes, so nearly every clause carries information. The telegraphic, verbless style with parenthetical field dumps makes it harder to parse than it needs to be, which costs it a point.

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?

With no output schema, ten optional parameters and multiple modes, the description carries the burden well by listing returned row fields, summary contents, ordering and pagination. It remains thin on failure and empty-result behavior, and on when the fallback name-matching should be avoided in favor of scheme_code.

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 still adds meaning beyond it — `compare` as bought-and-sold changes, `stock` as funds holding a symbol, `offset`/`top` as page mechanics, and the fallback chain that explains how fund/house/portfolio_code/statement_key relate to a prior ambiguous match. That is meaningful routing value over the field-level text.

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 opens with a concrete verb-and-resource framing — a fund's month-end portfolio — then enumerates exactly what comes back (holdings rows, net assets, summary buckets, debt YTM/durations), and adds distinct modes (`compare`, `stock`). That is enough to separate it from siblings such as get_mutual_fund and get_mutual_fund_nav_history without opening a schema.

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?

It routes among the tool's own lookup paths: by scheme_code, by fund name via a linked portfolio, else by name words matched to statements within 13 months, plus the `compare` and `stock` modes and their meanings. It does not explicitly say when to prefer this tool over the sibling fund/NAV tools, so it stops short of a full when/when-not statement.

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.