Skip to main content
Glama

Vaquill

by io.github.Vaquill-AI
OverviewDiscussionsAdmin

Resolve Indian Citations (Batch)

resolve_india_citations_batch
Read-only

Provision resolutions for a list of Indian legal citations, using the same resolver as resolve_india_citation. Use when several citations need resolving without individual calls. Accepts up to 50 distinct citations and 500 entries before deduplication. One citation failing does not invalidate the others. Unknown request fields are rejected rather than ignored. Cost: 2 credits.

Input Schema

NameRequiredDescriptionDefault
stateNoNarrow to one jurisdiction. Required for a State-universal title.
asAtDateNoThe date the conduct or document belongs to, as YYYY-MM-DD. This is how a caller says which side of the 2023 recodification they mean: without it, a criminal section number resolves to BOTH the old code and its replacement, because both are live law.
citationsYesCitation strings, as a lawyer would type them.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / state / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "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"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / state / enum
      Removed 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"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / asAtDate / format
      Added value: +"date"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/non-destructive/closed-world; the description adds substantive behavior the annotations cannot convey: deduplication ceilings, partial-failure semantics ('one citation failing does not invalidate the others'), strict rejection of unknown fields, and a 2-credit cost. This is exactly the extra context an agent needs before batching a costly call.

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 purpose and sibling routing, then limits and failure semantics; nearly every clause earns its place. The trailing 'Cost: 2 credits.' is slightly abrupt but valuable information, so the sizing is justified.

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, return values need no explanation, and the description covers the operational facts an agent needs: when to use it, capacity limits, partial-failure behavior, input strictness, and cost. Nothing material 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 description coverage is 100%, including a detailed explanation of asAtDate's role in the 2023 recodification, so the schema carries the parameter burden. The description adds nothing about state or asAtDate, making 3 the appropriate baseline.

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 (resolve), resource (Indian legal citations), and batch scope, and explicitly names the sibling resolver it shares behavior with (resolve_india_citation). An agent can distinguish it from the single-citation tool and from the many get_act_* siblings without opening the schema.

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?

Explicitly states the selecting condition ('Use when several citations need resolving without individual calls') and identifies the alternative resolver. The batch limits (50 citations, 500 entries) further help the agent decide whether this tool or the single-call variant fits the workload.

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

All Vaquill toolsInspect
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.

Resources