Skip to main content
Glama
rsi-ai-platform

rsi-search-pro-mcp

Official

http_post_form

Submit a POST form to AJAX endpoints that do not change the URL, retrieving JSON data from government dashboards when dropdowns are not reflected in query parameters.

Instructions

POST a form (application/x-www-form-urlencoded) and return the JSON.

The escape hatch for Year/Month/Product dropdowns on government dashboards
that don't change the page URL — the dropdown triggers an AJAX POST and
only renders the result client-side, so pdf_discover and web_fetch can't
see it. Use this when a landing page's dropdown isn't a `<select>` whose
value becomes a query param.

Example — PPAC prior-year (FY2025-26) petroleum consumption:
  url = "https://ppac.gov.in/AjaxController/getConsumptionPetroleumProductsChartData"
  form = {"financialYear": "2025-2026", "reportBy": "1", "pageId": "43"}
  referer = "https://ppac.gov.in/consumption/products-wise"
Returns the full FY2025-26 monthly JSON (April 2025 → March 2026).

Args:
    url: The POST endpoint (usually `/AjaxController/...` on gov sites).
    form: Form fields to submit.
    referer: Optional Referer header — many gov AJAX endpoints reject
             requests without one.
    parse: "json" / "text" / "auto" (default — try JSON, fall back to text).

Returns:
    {url, status, content_type, json (when parseable), text, fetched_at}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
formYes
refererNo
parseNoauto
Behavior4/5

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

No annotations, so description carries full burden. Explains that it's an escape hatch for client-side AJAX calls, mentions referer requirement, and describes parse behavior. Could add details on rate limits or auth, but covers key operational traits.

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?

Well-structured with summary, context, example, and args/returns sections. Front-loaded with core functionality. Slightly verbose but every sentence contributes; minor redundancy in the example could be trimmed.

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?

No output schema, so description includes return format. Covers all key aspects: URL, form, referer, parse. Differentiates from siblings and provides a realistic example. Lacks error handling details, but sufficient for typical usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description thoroughly explains each parameter (url, form, referer, parse) with example values and purpose. Clarifies that referer is often required and parse has three modes. Adds significant value beyond schema types.

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?

Explicitly states it POSTs a form with content type application/x-www-form-urlencoded and returns JSON. Distinguishes from sibling tools pdf_discover and web_fetch by targeting AJAX POSTs that don't change the page URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'Use this when a landing page's dropdown isn't a <select> whose value becomes a query param.' Names sibling tools that cannot handle such cases, and includes a concrete example with a government site.

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/rsi-ai-platform/rsi-search-pro-mcp'

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