Vaquill

Defined Terms in an Act

india_act_definitions

Read-only

Extracted defined terms and their defining provisions, plus a separate definitionSections list. Use when a question turns on an act's own meaning of a term. Extraction covers only a minority of acts, so an empty result does not mean the act defines nothing. definitionSections identifies provisions to read even without extracted terms. terms is paged, but definitionSections is not. 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]+$"
```

Changed4 schema fields changedSep 14, 2026

changedInput schema / properties / act_id / examples

Previous value: -[
-  "IND_state_17068"
-]New value: +[
+  "IND_central_2114"
+]

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both.",
+  "examples": [
+    25
+  ]
+}

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

Behavior4/5

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

With readOnlyHint/openWorldHint=false/destructiveHint=false already covering the safety profile, the description adds non-obvious behavior: partial extraction coverage, the cost of 2 credits, and the asymmetric pagination (terms paged, definitionSections not). It doesn't explain return shape, but that's largely covered by the output schema.

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?

Front-loaded with the core purpose, then caveats and cost. Five short clauses with no wasted filler, though the terse fragment style ('terms is paged, but definitionSections is not. Cost: 2 credits.') is compact to the point of choppiness.

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?

An output schema exists, so return values needn't be explained. Combined with annotations, the description covers coverage limits, cost, pagination asymmetry, and the fallback field — enough for correct invocation. One gap: it doesn't reconcile the act_id parameter (schema example/detail drift toward section identifiers) which could confuse an agent.

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 baseline is 3; the schema already documents page, limit, pageSize and act_id. The description's mention that 'terms is paged, but definitionSections is not' adds useful scoping context but no new syntax for individual parameters.

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?

States a specific verb+resource: extracts defined terms with their defining provisions, plus a separate definitionSections list. An agent can distinguish it from generic section/text siblings like get_act_text or get_act_section_body. It doesn't explicitly name an alternative tool, so it falls short of a 5.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('when a question turns on an act's own meaning of a term'), plus an important when-not-to-conclude rule: empty results don't mean the act defines nothing since extraction covers only a minority of acts. It also tells the agent to fall back to definitionSections when terms are absent.

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.