kite-connect-mcp

User profile

get_profile

Read-onlyIdempotent

Retrieve the logged-in user's Kite profile, including identity, broker, enabled exchanges/products/order types, and demat consent/POA status for account checks.

Instructions

The logged-in user's Kite profile: user id, name, email, broker, the exchanges, products and order types enabled for the account, and whether it is a demat consent / POA account (meta.demat_consent).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the payload contents, including the specific `meta.demat_consent` field that tells the caller whether the account is a POA/demat-consent account, and by implying the authentication requirement.

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?

A single front-loaded sentence identifies the subject immediately, then lists the fields in a compact run-on list. Slightly dense, but no sentence is wasted and nothing is repeated from the name or title.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so field by field, including a nested meta field. What remains unstated is error behavior (e.g. what happens without a valid session) and the exact shape of the enabled exchanges/products/order types collections.

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?

The tool takes no parameters, and the schema coverage is 100%, so there is nothing parameter-related for the description to clarify. The description correctly stays focused on the return payload instead of inventing inputs.

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?

The description names a specific resource (the logged-in user's Kite profile) and enumerates exactly what it returns: user id, name, email, broker, enabled exchanges/products/order types, and demat consent. That is enough to separate it from data-fetching siblings like get_margins or get_holdings, though it does not explicitly name which sibling to use for adjacent account information.

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 only implied: the phrase 'logged-in user's' signals that a session must exist, which is the main precondition. There is no explicit statement of when to call this versus session_status or the margins tools, and no exclusions or alternatives are offered.

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