Vaquill

India Act Subordinate

india_act_subordinate

Read-only

Subordinate instruments the publisher records as made under this act: rules, regulations, notifications and orders.

Cost: 2 credits. An act with no subordinate instruments on record is the answer and is charged.

🔴 Resolved by the parent's TITLE. The stored parent_act_id is India Code's own identifier and does not address this corpus, so a hard link would resolve to nothing. Title matching reaches a served parent for most instruments that name one, and matchBasis says so on every response.

Paged with page + pageSize. total counts distinct INSTRUMENTS across all pages, not the rows on this page (returned) and not matching passages.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page number.
`limit`	No	DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both.
`act_id`	Yes	Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable from a citation but the CHAPTER is not, so hand-built ids usually 404.
`pageSize`	No	Rows per page (1-100). Defaults to 25.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 14, 2026

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / limit / default
```
Removed value: -25
```

changedInput schema / properties / limit / description

Previous value: -"Rows to return."New value: +"DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both."

removedInput schema / properties / limit / maximum
```
Removed value: -100
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```
removedInput schema / properties / limit / type
```
Removed value: -"integer"
```

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "1-based page number.",
+  "examples": [
+    1
+  ],
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Rows per page (1-100). Defaults to 25.",
+  "examples": [
+    25
+  ]
+}

AddedSep 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description discloses the 2-credit cost, the charged empty-result case, the parent-title resolution behavior, and the meaning of `total` as distinct instruments rather than rows or passages. This goes well beyond the `readOnlyHint` and `openWorldHint` annotations and gives agents important non-obvious behavioral facts.

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?

Every sentence earns its place: the core resource is front-loaded, followed by cost, the parent-resolution caveat, and pagination semantics. Despite carrying many caveats, the description is compact and well-structured.

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?

For a read-only paged list tool with an output schema, the description covers the non-obvious behaviors an agent needs: cost, empty-result charging, parent resolution limitations, and total-vs-returned counting. No critical gap is apparent.

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?

All 4 parameters have schema descriptions, so the 100% coverage baseline applies. The description does not add new input-specific semantics beyond what the schema already says; the pagination and `total` details are about response behavior rather than parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line clearly identifies the resource (subordinate instruments: rules, regulations, notifications and orders) and an act-specific scope. However, it is phrased as a noun phrase rather than an explicit verb like 'List' or 'Get', and it does not contrast with sibling tools.

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

Usage Guidelines3/5

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

No alternative tools are named, and there is no explicit condition for choosing this tool over siblings such as `india_act_definitions` or `get_act_amendments`. The description does provide useful operational context about parent-title resolution and pagination, but the primary use case is only implied.

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.