Skip to main content
Glama
rithik-cmyk

ecourts-mcp-server

by rithik-cmyk

Search Court Cases

ecourts_search_cases
Read-onlyIdempotent

Search Indian court cases using text queries, filters, date ranges, and year filters. Returns matching cases with CNR, parties, dates, and facet counts.

Instructions

Search for Indian court cases with text queries, filters, date ranges, year filters, and faceted aggregations.

Text search args (all optional): query, advocates, judges, petitioners, respondents, litigants

Filter args (arrays): court_codes, case_types, case_statuses, judicial_sections, case_categories, bench_types

Year filters (integer arrays): filing_years, registration_years, first_hearing_years, next_hearing_years, decision_years

Date ranges (YYYY-MM-DD): filing_date_from/to, registration_date_from/to, first_hearing_date_from/to, next_hearing_date_from/to, decision_date_from/to

Controls: include_facet_counts (bool), sort_by, sort_order, page, page_size (max 100)

Returns: matching cases with CNR, parties, dates, facet counts. Supply at least one search term or filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based)
queryNoGeneral full-text search across all fields
judgesNoSearch by judge name
sort_byNoField to sort by
advocatesNoSearch by advocate name (both petitioner and respondent advocates)
litigantsNoSearch petitioners AND respondents simultaneously
page_sizeNoResults per page (max 100)
case_typesNoFilter by case types: CIVIL, CRIMINAL, WRIT, APPEAL, REVISION, EXECUTION, ARBITRATION, MATRIMONIAL, MOTOR_ACCIDENT, LABOR
sort_orderNoSort direction
bench_typesNoFilter by bench type, e.g. ['SINGLE','DIVISION']
court_codesNoFilter by court codes, e.g. ['DLHC01','HCBM01']. Use ecourts_get_court_structure or the enum reference.
petitionersNoSearch by petitioner name
respondentsNoSearch by respondent name
filing_yearsNoFilter by filing year(s), e.g. [2024, 2023]
case_statusesNoFilter by statuses: PENDING, DISPOSED, TRANSFERRED, WITHDRAWN, UNKNOWN
decision_yearsNoFilter by decision year(s)
filing_date_toNoFiling date range end (YYYY-MM-DD)
case_categoriesNoFilter by case categories, e.g. ['COMMERCIAL']
decision_date_toNoDecision date range end (YYYY-MM-DD)
filing_date_fromNoFiling date range start (YYYY-MM-DD)
judicial_sectionsNoFilter by judicial sections: CIV, CRIM, WRIT, REV, APP, MISC, PIL, BAIL, URG, ADM
decision_date_fromNoDecision date range start (YYYY-MM-DD)
next_hearing_yearsNoFilter by next hearing year(s)
registration_yearsNoFilter by registration year(s)
first_hearing_yearsNoFilter by first hearing year(s)
include_facet_countsNoInclude facet (aggregation) counts in response. Default true.
next_hearing_date_toNoNext hearing date range end (YYYY-MM-DD)
registration_date_toNoRegistration date range end (YYYY-MM-DD)
first_hearing_date_toNoFirst hearing date range end (YYYY-MM-DD)
next_hearing_date_fromNoNext hearing date range start (YYYY-MM-DD)
registration_date_fromNoRegistration date range start (YYYY-MM-DD)
first_hearing_date_fromNoFirst hearing date range start (YYYY-MM-DD)
Behavior4/5

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

Annotations indicate read-only, open-world, idempotent, non-destructive. Description adds details on parameter constraints (max page size, date format), facet counts, and return fields, complementing the safety profile without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with bullet points, clear category headers, and no extraneous text. It efficiently conveys all necessary information for a complex tool.

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?

Given the tool's complexity (32 parameters, no output schema), the description covers all parameter groups, constraints, and typical usage. It lacks explicit pagination or error details but is sufficient for agent invocation.

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

Parameters4/5

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

Schema has 100% description coverage. The description groups parameters into logical categories (text, filters, years, dates, controls), adding semantic structure that aids understanding beyond individual schema descriptions.

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 it searches for Indian court cases with various criteria, listing supported query types and return fields. It distinguishes from sibling tools (causelist dates, specific case retrieval) by focusing on search and filtering.

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?

The description requires at least one search term or filter, and categorizes parameters into text, filters, dates, etc. It does not explicitly compare to alternatives but the purpose is clear relative to sibling tool names.

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/rithik-cmyk/ecourts-mcp-server'

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