rti-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RTI_MCP_HOME | No | Config + cache location | ~/.rti-mcp |
| RTI_HISTORY_URL | No | Seed View History URL (fallback if no config file) | |
| RTI_MCP_CACHE_TTL | No | Seconds a fetched list stays fresh | 900 |
| RTI_MCP_DOWNLOAD_DIR | No | Where PDFs and CSVs land | ~/.rti-mcp/documents |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rti_session_statusA | Check whether the stored RTI Online session URL still works, and show whose account it belongs to plus how stale the cached lists are. Run this first when other tools report authentication problems. |
| rti_set_session_urlA | Store a new RTI Online 'View History' session URL, replacing any previous one and clearing cached data. Use when the old URL stops working: the user logs in at rtionline.gov.in with OTP + captcha, clicks 'View History', and copies the full address-bar URL. |
| rti_dashboardC | Registered / disposed / pending totals for the citizen's RTI requests and first appeals -- the summary shown on the View History dashboard. |
| rti_listA | List RTI applications in one bucket. category: 'request' or 'appeal'; status: 'registered' (all of them), 'disposed' or 'pending'. Optional |
| rti_searchA | Search every RTI request and appeal by registration number fragment, public-authority code, status text, filing date or status date; dates match in either 2026-08-07 or 07/08/2026 form. Use this when the user names an application loosely (e.g. 'the BSNL one', 'NIMHANS') or asks what moved on a given day. |
| rti_overdueA | Pending RTI requests whose reply is overdue. The RTI Act gives a public authority 30 days to reply, so |
| rti_statusA | Current status of one RTI application by registration number (e.g. 'NIMNS/R/E/26/00220') -- the state, the date it changed, the public authority's remarks or reply summary, and whether a reply PDF is available. This is the everyday 'what happened to my RTI' lookup. |
| rti_detailsA | Full filed details of one RTI application by registration number: public authority, the complete text of information sought, applicant particulars, BPL status, concerned CPIO and any attached document. Use |
| rti_downloadA | Download an application's PDF to disk. kind='reply' fetches the public authority's reply (only on disposed applications); kind='request' fetches the document attached to the original request. Returns the saved path; defaults to the server's documents folder. |
| rti_export_csvB | Export every RTI request and appeal to a CSV file for tracking or analysis -- registration number, applicant, filing date, current status and status date. |
| rti_clear_cacheA | Drop all cached application lists so the next query re-reads the portal. Normally unnecessary -- tools take a refresh flag. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: session management, dashboard summary, list, search, overdue, single status, full details, download, export, and cache clearing. The overlap between rti_status and rti_details is resolved by their descriptions.
All tool names share the rti_ prefix, making them easy to recognize. However, the action words mix nouns (status, details, dashboard) with verbs (download, export_csv, clear_cache), which is a minor inconsistency from a strict verb_noun convention.
11 tools is well within the ideal 3-15 range for a focused portal-interaction server. Each tool covers a necessary operation without unnecessary bloat.
The tool surface is complete for its stated purpose: managing and tracking RTI applications. It covers session setup, verification, browsing, searching, detailed lookup, downloads, and export — no obvious dead ends.