Vaquill

Rules Made Under an Act

india_act_subordinate

Read-only

Paged rules, regulations, notifications and orders the publisher records as made under an act. Use when looking beyond the parent statute to its subordinate instruments. Matching uses the parent's title, not parent_act_id, which is an India Code identifier that does not address this corpus. Check matchBasis. total counts distinct instruments across all pages, while returned counts rows on this page. Cost: 2 credits.

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.

Changed1 schema field changedOct 1, 2026
- changedInput schema / properties / act_id / pattern
```
Previous value: -"^[a-zA-Z0-9_-]+$"New value: +"^[^/\\\\\\x00-\\x1f]+$"
```

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.3/5.0

Behavior4/5

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

Annotations already establish a safe read-only, non-open-world operation, and the description adds genuinely useful behavior beyond that: the parent-title matching quirk (with a nudge to check matchBasis), the distinction that 'total counts distinct instruments across all pages, while returned counts rows on this page', and a stated cost of 2 credits. It does not cover failure modes for unmatched titles or rate limits, so it falls short of a 5.

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?

Everything is front-loaded – purpose first, then the matching caveat, then the count semantics and cost. Each sentence carries information, though the compressed phrasing ('Matching uses the parent's title, not parent_act_id') is dense and relies on the reader parsing a negation mid-sentence.

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?

With an output schema present, return-value explanation is not required, and the description still usefully clarifies the total/returned fields. Combined with paging, cost, and the matching caveat, an agent has enough to invoke it correctly; only edge-case behavior (e.g., what happens when no subordinate instruments match) is unaddressed.

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 coverage is 100%, so the baseline would be 3, but the description adds real meaning: it warns that matching uses the parent's title, not parent_act_id, which resolves ambiguity left by the act_id schema text (whose examples and wording reference section/USC citation ids). It does not document page/limit/pageSize, which the schema already handles.

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 names a specific verb+resource combination – paged rules, regulations, notifications and orders made under an act – and its scope ('subordinate instruments') clearly distinguishes it from siblings like get_act_text, get_act_amendments, and get_act_structure, which address the parent statute.

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 gives an explicit when-to-use condition ('Use when looking beyond the parent statute to its subordinate instruments') and a crucial caveat about matching by parent title rather than parent_act_id. It stops short of naming specific alternative tools to prefer in other circumstances, so it is clear context but not full when/when-not routing.

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.