Vaquill

Acts Citing This One

india_act_cited_by

Read-only

Paged inbound citations from provisions elsewhere in the corpus that name an act. Use when finding provisions that mention the act, rather than following its outbound references. Matching uses the act's title, not its identifier, so title variants and line breaks can be missed. Read matchBasis and treat results as a floor. total counts distinct citing provisions across all pages. 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.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), but the description adds substantial beyond-schema behavior: title-based matching that can miss variants and line breaks, an instruction to read matchBasis and treat results as a floor, the meaning of total across pages, and a credit cost of 2. This is rich recall/pagination/cost disclosure.

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?

Short, front-loaded sentences: purpose first, then the usage disambiguation, then matching caveats, then pagination semantics and cost. Every sentence carries distinct information with no filler.

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?

With an output schema present, the description needn't explain return shape, and it still volunteers the critical caveats an agent needs (title-match recall risk, matchBasis, floor interpretation, per-page total). Nothing material is missing for correct invocation and interpretation.

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 description coverage is 100%, so page, limit, pageSize, and act_id are all documented in the schema itself. The description adds only the semantics of the returned total, not parameter guidance, so the baseline 3 is appropriate.

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?

States a specific verb+resource (paged inbound citations naming an act) and immediately disambiguates direction by contrasting with 'following its outbound references.' An agent can distinguish this from sibling reference tools like india_section_references or get_corresponding_provisions without opening a schema.

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?

Explicitly says when to use it ('finding provisions that mention the act') and implicitly excludes the outbound direction, which is clear context. It stops short of naming the specific sibling tool to use for outbound references, so it isn't fully prescriptive.

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.