kite-connect-mcp

Mutual fund SIPs

get_mf_sips

Read-onlyIdempotent

Retrieve mutual fund SIP details, either for one SIP by ID or all active and paused SIPs with status counts, including instalment amounts, frequency, and next payment dates.

Instructions

Mutual fund SIPs (recurring purchases): with sip_id one SIP, else all active and paused ones with status_counts. Each has sip_id, tradingsymbol (ISIN), fund, status (ACTIVE, PAUSED, CANCELLED), instalment_amount (INR), frequency (weekly, monthly, quarterly), instalment_day (monthly only, else 0), instalments (the number planned; -1 means until cancelled), completed_instalments, pending_instalments, next_instalment, last_instalment and tag.

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_mf_sips"
  }
}

Input Schema

Name	Required	Description
`limit`	No	items per page
`offset`	No	items to skip
`sip_id`	No	one SIP; omit to list them all

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — it discloses that the list mode excludes CANCELLED SIPs even though CANCELLED is a possible status value, and that status_counts is returned. It omits any statement about pagination behavior or ordering, leaving a gap for a list tool whose schema allows up to 500 items.

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 purpose and the mode switch in the first clause, then a single dense enumeration of returned fields. Every element is informative given there is no output schema, though the field list is a fairly long unbroken run that could be grouped more scan-ably.

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, describing each returned field (sip_id, tradingsymbol as ISIN, instalment_amount in INR, instalments=-1 meaning open-ended, dates) is exactly what the agent needs to interpret results. The remaining gap is pagination/ordering behavior, which is only implicit in the limit/offset schema fields.

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 slightly beyond by qualifying what 'all' means (active and paused only) and by decoding sip_id as selecting exactly one record, which affects result interpretation. limit/offset are left entirely to the schema.

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-equivalent (retrieve) and resource (mutual fund SIPs), and immediately splits the two behaviors: 'with sip_id one SIP, else all active and paused ones with status_counts'. The sibling list contains adjacent tools (get_mf_holdings, get_mf_orders) and this definition makes clear it is about recurring SIP plans, not holdings or orders.

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?

Explicitly tells the agent how to select each mode: pass sip_id for a single SIP, omit it to list all. It does not, however, steer the agent away from get_mf_orders/get_mf_holdings when it wants transactions versus plans, so there is no true alternative routing.

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