Skip to main content
Glama
rehan1020

mcp-india-stack

by rehan1020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lookup_bbps_biller

Read-onlyIdempotent

Identify BBPS biller details for electricity, gas, DTH, water, broadband, FASTag, insurance, and mobile recharges by filtering with category, state, or biller ID.

Instructions

Look up BBPS (Bharat Bill Payment System) biller details.

Use when setting up bill payments for electricity, gas, DTH, water, broadband, FASTag, insurance, or mobile recharges.

Args: category: Category of biller to filter by. state: State to filter by (or 'all' for pan-India). biller_id: Direct biller ID for specific lookup.

Returns: Standard envelope with matching billers and parameter schemas.

Notes: Data is bundled offline. For real-time directory, check NPCI BBPS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoState name (e.g., 'Maharashtra', 'Delhi') or 'all'
categoryNoelectricity, gas, dth, water, broadband, fastag, insurance, mobile
biller_idNoDirect biller ID lookup

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / biller_id / title
      Added value: +"Biller Id"
    • addedInput schema / properties / category / title
      Added value: +"Category"
    • addedInput schema / properties / state / title
      Added value: +"State"
    • addedInput schema / title
      Added value: +"lookup_bbps_billerArguments"
    • addedOutput schema / title
      Added value: +"lookup_bbps_billerDictOutput"
  2. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already signal read-only and idempotent behavior. The description adds meaningful context by noting the data is bundled offline, so agents know it is not a real-time directory, and by describing the return as a standard envelope with matching billers and parameter schemas.

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?

The description is well-organized with purpose, usage, args, returns, and notes sections, and the most important caveat is placed last in Notes. The Args section somewhat duplicates the schema descriptions, but the overall length is still reasonable and front-loaded with the tool purpose.

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 a read-only, idempotent lookup tool with 0 required parameters and an output schema, the description provides enough guidance for an agent to invoke it correctly. It covers the use case, filtering options, result shape, and the critical offline-data limitation.

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?

The input schema already documents all three parameters with 100% coverage. The description mostly restates the same semantics, such as filtering by category, using 'all' for state, and direct lookup by biller_id. This provides minimal additional meaning beyond 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?

The description clearly states a specific action and resource: look up BBPS biller details. The list of supported payment categories further clarifies what the tool covers, distinguishing it from sibling validator and calculator tools.

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 explicitly says to use this when setting up bill payments for utilities, DTH, broadband, FASTag, insurance, or mobile recharges. It also warns that the data is bundled offline and directs users to NPCI BBPS for real-time directory lookup, but it does not compare directly with sibling tools like lookups for IFSC, bank, pincode, or HSN.

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

Deploy Server

Other Tools