Vaquill

Browse Indian Acts

list_acts

Read-only

Browse and filter enactments rather than searching their text: by jurisdiction (central or a state), issuing regulator, year and status. Use when the user wants to know WHAT exists in an area before asking what it says, or to confirm an Act's exact title before citing it. Cost: 1 credit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	1-based page number.
`sort`	No	Sort order. `popular` is DEPRECATED and behaves as `year_desc`: it ordered by a read counter held only in the retired store. Values: `year_desc`, `year_asc`, `title_asc`, `title_desc`, `popular`.	year_desc
`state`	No	Jurisdiction slug. `central` is a value here, for Union legislation. Live counts per jurisdiction are on GET /acts/coverage.
`search`	No	Keep only acts whose title contains this substring, matched case-insensitively. A title filter, not a search over the text: use POST /acts/search for that.
`status`	No	The publisher's lifecycle status for the act. Their claim, not our verdict: see GET /acts/{actId}/status. Values: `in_force`, `repealed`, `superseded`, `spent`.
`yearTo`	No	Latest year of enactment to include, inclusive.
`category`	No	Jurisdictional class of the instrument. `repealed` and `spent` are accepted for backward compatibility and resolve against the act's status instead. Values: `central`, `state`, `regulatory`, `repealed`, `spent`.
`pageSize`	No	Results per page (1-100).
`yearFrom`	No	Earliest year of enactment to include, inclusive. Matched against the publisher's own year field, which is occasionally corrupt, so there is no lower bound and a value below 1800 is a legitimate way to find those rows.
`department`	No	Issuing body. Deliberately NOT an enumerated list: this field holds 943 distinct values and mixes clean regulator slugs (`sebi`, `rbi`, `moefcc`) with free-text state department names (`Law Department`). Read GET /acts/filters for the values with the most data behind them.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedSep 14, 2026

changedInput schema / properties / category / description

Previous value: -"Jurisdictional class."New value: +"Jurisdictional class of the instrument. `repealed` and `spent` are accepted for backward compatibility and resolve against the act's status instead. Values: `central`, `state`, `regulatory`, `repealed`, `spent`."

changedInput schema / properties / department / description

Previous value: -"Issuing body. Free text rather than a list: 943 distinct values, mixing regulator slugs with state department names. See GET /acts/filters."New value: +"Issuing body. Deliberately NOT an enumerated list: this field holds 943 distinct values and mixes clean regulator slugs (`sebi`, `rbi`, `moefcc`) with free-text state department names (`Law Department`). Read GET /acts/filters for the values with the most data behind them."

changedInput schema / properties / page / description

Previous value: -"Page number"New value: +"1-based page number."

addedInput schema / properties / page / examples
```
Added value: +[
+  1
+]
```

changedInput schema / properties / pageSize / description

Previous value: -"Results per page (1-100)"New value: +"Results per page (1-100)."

addedInput schema / properties / pageSize / examples
```
Added value: +[
+  50
+]
```

changedInput schema / properties / search / description

Previous value: -"Filter by title substring"New value: +"Keep only acts whose title contains this substring, matched case-insensitively. A title filter, not a search over the text: use POST /acts/search for that."

addedInput schema / properties / search / examples
```
Added value: +[
+  "income tax"
+]
```

changedInput schema / properties / sort / description

Previous value: -"Sort order. `popular` is DEPRECATED and behaves as `year_desc`: it ordered by a read counter held only in the retired store."New value: +"Sort order. `popular` is DEPRECATED and behaves as `year_desc`: it ordered by a read counter held only in the retired store. Values: `year_desc`, `year_asc`, `title_asc`, `title_desc`, `popular`."

changedInput schema / properties / state / description

Previous value: -"Jurisdiction slug. `central` is a value here."New value: +"Jurisdiction slug. `central` is a value here, for Union legislation. Live counts per jurisdiction are on GET /acts/coverage."

changedInput schema / properties / status / description

Previous value: -"The publisher's lifecycle status for the act."New value: +"The publisher's lifecycle status for the act. Their claim, not our verdict: see GET /acts/{actId}/status. Values: `in_force`, `repealed`, `superseded`, `spent`."

changedInput schema / properties / yearFrom / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 2100,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / yearFrom / description

Previous value: -"Minimum year (inclusive)"New value: +"Earliest year of enactment to include, inclusive. Matched against the publisher's own year field, which is occasionally corrupt, so there is no lower bound and a value below 1800 is a legitimate way to find those rows."

addedInput schema / properties / yearFrom / examples
```
Added value: +[
+  2015
+]
```

changedInput schema / properties / yearTo / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 2100,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / yearTo / description

Previous value: -"Maximum year (inclusive)"New value: +"Latest year of enactment to include, inclusive."

addedInput schema / properties / yearTo / examples
```
Added value: +[
+  2024
+]
```

Changed14 schema fields changedSep 7, 2026

changedInput schema / properties / category / description

Previous value: -"Filter: central, state, regulatory, repealed, spent"New value: +"Jurisdictional class."

addedInput schema / properties / category / enum

Added value: +[
+  "central",
+  "state",
+  "regulatory",
+  "repealed",
+  "spent"
+]

addedInput schema / properties / category / examples
```
Added value: +[
+  "central"
+]
```

changedInput schema / properties / department / description

Previous value: -"Filter by regulatory body (e.g. 'sebi', 'rbi')"New value: +"Issuing body. Free text rather than a list: 943 distinct values, mixing regulator slugs with state department names. See GET /acts/filters."

addedInput schema / properties / department / examples
```
Added value: +[
+  "sebi"
+]
```

changedInput schema / properties / sort / description

Previous value: -"Sort: year_desc, year_asc, title_asc, title_desc, popular"New value: +"Sort order. `popular` is DEPRECATED and behaves as `year_desc`: it ordered by a read counter held only in the retired store."

addedInput schema / properties / sort / enum

Added value: +[
+  "year_desc",
+  "year_asc",
+  "title_asc",
+  "title_desc",
+  "popular"
+]

addedInput schema / properties / sort / examples
```
Added value: +[
+  "title_asc"
+]
```

changedInput schema / properties / state / description

Previous value: -"Filter by state slug (e.g. 'maharashtra', 'delhi')"New value: +"Jurisdiction slug. `central` is a value here."

addedInput schema / properties / state / enum

Added value: +[
+  "andaman-and-nicobar-islands",
+  "andaman-nicobar",
+  "andhra-pradesh",
+  "arunachal-pradesh",
+  "assam",
+  "bihar",
+  "central",
+  "chandigarh",
+  "chhattisgarh",
+  "dadra-and-nagar-haveli-and-daman-and-diu",
+  "dadra-nagar-haveli",
+  "delhi",
+  "goa",
+  "gujarat",
+  "haryana",
+  "himachal-pradesh",
+  "jammu-and-kashmir",
+  "jammu-kashmir",
+  "jharkhand",
+  "karnataka",
+  "kerala",
+  "ladakh",
+  "lakshadweep",
+  "madhya-pradesh",
+  "maharashtra",
+  "manipur",
+  "meghalaya",
+  "mizoram",
+  "nagaland",
+  "odisha",
+  "puducherry",
+  "punjab",
+  "rajasthan",
+  "sikkim",
+  "tamil-nadu",
+  "telangana",
+  "tripura",
+  "uttar-pradesh",
+  "uttarakhand",
+  "west-bengal"
+]

addedInput schema / properties / state / examples
```
Added value: +[
+  "maharashtra"
+]
```

changedInput schema / properties / status / description

Previous value: -"Filter: in_force, repealed, spent"New value: +"The publisher's lifecycle status for the act."

addedInput schema / properties / status / enum

Added value: +[
+  "in_force",
+  "repealed",
+  "superseded",
+  "spent"
+]

addedInput schema / properties / status / examples
```
Added value: +[
+  "repealed"
+]
```

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds the non-obvious behavioral detail that it costs 1 credit, which is useful beyond the readOnlyHint annotation. It also clarifies that filters apply to what exists, not the text. No contradiction with annotations.

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 three concise sentences: first the function, then the use cases, then the cost. Nothing is extraneous, and the key distinctions appear up front.

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?

The tool has an output schema, a full parameter schema, and readOnlyHint annotations. The description adequately fills the remaining gaps: helps you decide when to use it (browsing vs searching), explains the cost, and points to a filter scope. No essential behavior for selecting or invoking it 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%, so each parameter already has a detailed description. The tool description adds a high-level abstract of filter dimensions (jurisdiction, regulator, year, status) but does not add meaning beyond what the schema already offers.

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 the tool browses and filters enactments by jurisdiction, regulator, year, and status. It explicitly contrasts this with searching the text, distinguishing it from the sibling search tools. An agent can immediately identify this as the 'what exists' listing tool.

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?

It provides clear use cases ('when the user wants to know WHAT exists' or 'confirm an exact title') and implicitly separates this from text search ('rather than searching their text'). However, it does not name alternative siblings such as search_acts explicitly, so when-not guidance is implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vaquill tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.