Skip to main content
Glama

India Get Tender

india_get_tender
Read-onlyIdempotent

Full details of one Indian government tender by its portal tender ID (e.g. "2026_IAF_792147_1") from the official GePNIC e-procurement portal that published it, tender type and category, form of contract, EMD amount, tender fee, tender value, product category, work description, location and pincode, pre-bid meeting, all key dates (IST), and the organisation chain. Take the tender_id and portal from india_defence_tenders or india_search_tenders; passing the organisation makes the lookup much faster.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "portal": "defence",
      "tender_id": "2026_IAF_792037_1",
      "organisation": "Air Force"
    },
    "name": "india_get_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
portalNoPortal the tender is on (default "defence"). "defence" = Ministry of Defence e-Procurement (defproc.gov.in); "central" = Central Public Procurement Portal, central government (eprocure.gov.in/eprocure); "cpse" = Central PSU e-Tenders (etenders.gov.in); "maharashtra" = Maharashtra e-Tenders (mahatenders.gov.in); "tamil-nadu" = Tamil Nadu e-Tenders (tntenders.gov.in); "kerala" = Kerala e-Tenders (etenders.kerala.gov.in); "west-bengal" = West Bengal e-Tenders (wbtenders.gov.in); "rajasthan" = Rajasthan e-Procurement (eproc.rajasthan.gov.in); "delhi" = Government of NCT of Delhi e-Procurement (govtprocurement.delhi.gov.in); "coal-india" = Coal India e-Tenders (coalindiatenders.nic.in); "iocl" = Indian Oil Corporation e-Tenders (iocletenders.nic.in); "pmgsy" = PMGSY rural roads e-Tenders (pmgsytenders.gov.in).
tender_idYesPortal tender ID, e.g. "2026_IAF_792147_1" (the last bracketed value in a listing).
organisationNoOptional organisation substring to narrow the lookup, e.g. "Air Force".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / portal / description
      Previous value: -"Portal the tender is on (default \"defence\"). \"defence\" = Ministry of Defence e-Procurement (defproc.gov.in); \"central\" = Central Public Procurement Portal — central government (eprocure.gov.in/eprocure); \"cpse\" = Central PSU e-Tenders (etenders.gov.in); \"maharashtra\" = Maharashtra e-Tenders (mahatenders.gov.in); \"tamil-nadu\" = Tamil Nadu e-Tenders (tntenders.gov.in); \"kerala\" = Kerala e-Tenders (etenders.kerala.gov.in); \"west-bengal\" = West Bengal e-Tenders (wbtenders.gov.in); \"rajasthan\" = Rajasthan e-Procurement (eproc.rajasthan.gov.in); \"delhi\" = Government of NCT of Delhi e-Procurement (govtprocurement.delhi.gov.in); \"coal-india\" = Coal India e-Tenders (coalindiatenders.nic.in); \"iocl\" = Indian Oil Corporation e-Tenders (iocletenders.nic.in); \"pmgsy\" = PMGSY rural roads e-Tenders (pmgsytenders.gov.in)."New value: +"Portal the tender is on (default \"defence\"). \"defence\" = Ministry of Defence e-Procurement (defproc.gov.in); \"central\" = Central Public Procurement Portal, central government (eprocure.gov.in/eprocure); \"cpse\" = Central PSU e-Tenders (etenders.gov.in); \"maharashtra\" = Maharashtra e-Tenders (mahatenders.gov.in); \"tamil-nadu\" = Tamil Nadu e-Tenders (tntenders.gov.in); \"kerala\" = Kerala e-Tenders (etenders.kerala.gov.in); \"west-bengal\" = West Bengal e-Tenders (wbtenders.gov.in); \"rajasthan\" = Rajasthan e-Procurement (eproc.rajasthan.gov.in); \"delhi\" = Government of NCT of Delhi e-Procurement (govtprocurement.delhi.gov.in); \"coal-india\" = Coal India e-Tenders (coalindiatenders.nic.in); \"iocl\" = Indian Oil Corporation e-Tenders (iocletenders.nic.in); \"pmgsy\" = PMGSY rural roads e-Tenders (pmgsytenders.gov.in)."
  2. First observed

TDQS

A3.9/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 safety is covered. The description adds the meaningful behavioral detail that including organisation 'makes the lookup much faster', but says nothing about failure behavior for an unknown ID or a mismatched portal.

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 core purpose, followed by a useful field inventory and one actionable sentence. The field enumeration is long but earns its place given there is no output schema; nothing is redundant with the 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?

With no output schema, listing the returned fields (EMD, tender fee, dates in IST, organisation chain) is genuinely necessary and present. Inputs and their upstream sources are covered; only error/edge-case behavior for an invalid or cross-portal ID is missing.

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?

Schema coverage is 100% and the enum for portal is fully documented per-portal, so the schema carries most of the load. The description adds only marginal meaning beyond it — that tender_id must be the portal's own ID and that organisation acts as a speed accelerator rather than a filter requirement.

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 and resource — 'Full details of one Indian government tender by its portal tender ID' — plus the source system (GePNIC portal) and an example ID format. It also enumerates the returned fields, which makes it clearly distinguishable from the listing/search siblings.

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 where the inputs come from ('Take the tender_id and portal from india_defence_tenders or india_search_tenders') and adds a performance tip about passing organisation. It stops short of stating when not to use this tool (e.g. for browsing or filtering), so it is strong but not fully exhaustive.

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.