Skip to main content
Glama

Vaquill

by io.github.Vaquill-AI
OverviewDiscussionsAdmin

IPC/CrPC to BNS/BNSS Mapping

get_corresponding_provisions
Read-only

Map a repealed Indian criminal code to the 2023 code that replaced it, section by section: IPC to BNS and CrPC to BNSS, in force from 1 July 2024. Pass either side ('ipc' or 'bns' both work). Use whenever a source, a pleading or the user cites an old section number, so you answer under the provision actually in force rather than the repealed one. 'iea'/'bsa' return 404 until that mapping lands. Cost: 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_codeYes`ipc` and `bns` return the same mapping, as do `crpc` and `bnss`. Case-insensitive. `iea` and `bsa` are accepted but return 404 until their mapping is available.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / act_code / description
      Previous value: -"Either side of a recodification pair, matched case-insensitively so `IPC` and `ipc` are the same request. `ipc`/`bns` and `crpc`/`bnss` each return the same mapping; `iea`/`bsa` are accepted and 404 until that mapping lands. Values: `ipc`, `crpc`, `iea`, `bns`, `bnss`, `bsa`."New value: +"`ipc` and `bns` return the same mapping, as do `crpc` and `bnss`. Case-insensitive. `iea` and `bsa` are accepted but return 404 until their mapping is available."
  2. Changed3 schema fields changed
    • changedInput schema / properties / act_code / description
      Previous value: -"Act code: ipc, crpc, iea, bns, bnss or bsa"New value: +"Either side of a recodification pair, matched case-insensitively so `IPC` and `ipc` are the same request. `ipc`/`bns` and `crpc`/`bnss` each return the same mapping; `iea`/`bsa` are accepted and 404 until that mapping lands. Values: `ipc`, `crpc`, `iea`, `bns`, `bnss`, `bsa`."
    • addedInput schema / properties / act_code / enum
      Added value: +[
+  "ipc",
+  "crpc",
+  "iea",
+  "bns",
+  "bnss",
+  "bsa"
+]
    • addedInput schema / properties / act_code / examples
      Added value: +[
+  "ipc"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive and closed-world safety, so the bar is lower. The description still adds real context beyond them: a 1-credit cost, the 1 July 2024 in-force date, bidirectional input, and the failure mode for 'iea'/'bsa' (404).

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?

Four short sentences, each load-bearing: scope, effective date, usage trigger, known limitation, cost. Front-loaded with the mapping scope and 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, return values need no explanation. The description covers the effective date, bidirectionality, the accepted-but-unmapped codes, and the credit cost — everything an agent needs to call it correctly.

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% and the schema already documents case-insensitivity, the ipc/bns and crpc/bnss equivalence, and the iea/bsa 404. The description restates the bidirectional behavior but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 (map), specific resources (repealed IPC/CrPC to 2023 BNS/BNSS), and the granularity (section by section). This is clearly distinguishable from siblings like resolve_india_citation or get_act_section, which do not perform repealed-to-current mapping.

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?

Gives an explicit trigger: 'Use whenever a source, a pleading or the user cites an old section number', plus a rationale. It also notes a when-not condition ('iea'/'bsa' return 404). It stops short of naming a sibling tool as the alternative for citation resolution, so it is clear context rather than full routing.

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