Skip to main content
Glama

india_gsec_yields

Retrieve current India government securities yield curve from 91-day T-bill to 30-year bond, with real interest rate and data source links.

Instructions

India Government Securities (G-Sec) yield curve: 91-day T-bill to 30-year bond.

Bloomberg Terminal charges $31,980/year for government bond data. RBI and CCIL publish India G-Sec yields free.

Provides:

  • 91-day, 182-day, 364-day T-bill yields

  • 5-year, 10-year, 30-year G-Sec yields

  • Real interest rate (World Bank)

  • Live data source links (CCIL, RBI)

Examples: india_gsec_yields() → Current India government bond yield curve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It lists returned data but does not disclose update frequency, freshness, rate limits, or authentication needs. More behavioral context is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is somewhat lengthy with bullet points and a Bloomberg comparison. It starts with purpose but includes extra information that could be trimmed. Structure is adequate but not optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and an output schema, the description covers purpose and data returned. However, it lacks behavioral transparency (e.g., data freshness), leaving some gaps. Basic completeness but not thorough.

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?

No parameters exist, so schema coverage is trivial. Baseline for 0 params is 4. The description adds value by specifying what the tool returns, but no parametric explanation needed.

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 clearly identifies the tool as fetching India G-Sec yields, listing specific maturities and additional data. It distinguishes from siblings as no other tool in the list appears to provide G-Sec yields.

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 implies this is the tool for G-Sec yields by comparing with Bloomberg cost and mentioning free sources. However, it does not explicitly state when not to use or name sibling alternatives, though none exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/finstacklabs/finstack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server