Skip to main content
Glama

India Tender Organisations

india_tender_organisations
Read-onlyIdempotent

Lists the buying organisations on an official Indian government e-procurement portal (CPPP central, central PSUs, Ministry of Defence, or a state portal) with each one's live count of ACTIVE tenders, "which Indian ministries have open tenders", "how many active tenders does the Indian Army have", "biggest buyers on Maharashtra e-tenders". Use it to pick an organisation for india_search_tenders.

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"
    },
    "name": "india_tender_organisations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional organisation-name substring filter.
portalNoWhich portal (default "central"). "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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / portal / description
      Previous value: -"Which portal (default \"central\"). \"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: +"Which portal (default \"central\"). \"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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds real behavioral context beyond that: results come from live official portals and carry current active-tender counts, which sets expectations about freshness. It says nothing about result volume, pagination, or ordering by count, which is why it is not a 5.

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 verb and resource, and the quoted user-style questions are compact illustrations of capability. The middle clause is a long run-on list and one example ('biggest buyers on Maharashtra e-tenders') presumes an ordering the description never states.

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

Completeness5/5

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

Two optional parameters, no output schema, and a well-documented enum — the description supplies what is missing: what the rows conceptually contain (organisations plus active-tender counts) and how the result feeds the next tool. Nothing an agent needs in order to call it correctly is absent.

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 portal enum documents every portal with its hostname, so the description can only add marginal meaning. Naming the portal families (CPPP central, central PSUs, MoD, state portal) loosely maps to the enum but duplicates it; the example queries hint at substring-style filtering but do not describe the query parameter.

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 — lists buying organisations across named Indian portals — and adds the distinguishing payload: each organisation's live count of ACTIVE tenders. The quoted real-world queries make the intended output unambiguous.

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 routes the agent: 'Use it to pick an organisation for india_search_tenders', and the example queries imply the discovery-then-search workflow. It stops short of stating when not to use it (e.g. when the organisation name is already known and search can be called directly).

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.