Skip to main content
Glama

indian_legal_mcp_get_act_info

Get metadata about one specific Act: its full name, year enacted, and whether it is still current law or has been repealed and replaced by something newer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "act_code": "<act_code>"
    },
    "name": "indian_legal_mcp_get_act_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
act_codeYesshort code, e.g. BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA, RERA, CA, IBC, RTI, ITA, SEBI, SCRA, etc. (102 Acts supported).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / act_code / description
      Previous value: -"short code, e.g. BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA, RERA, CA, IBC, RTI, etc. (81 Acts supported)."New value: +"short code, e.g. BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA, RERA, CA, IBC, RTI, ITA, SEBI, SCRA, etc. (102 Acts supported)."
  2. Changed1 schema field changed
    • changedInput schema / properties / act_code / description
      Previous value: -"short code, one of BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA."New value: +"short code, e.g. BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA, RERA, CA, IBC, RTI, etc. (81 Acts supported)."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the return payload's most consequential element: whether the Act is still current law or has been repealed and replaced. It does not cover failure behavior for an unknown act_code or confirm the operation is a pure read, so it is good but not exhaustive.

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?

One front-loaded sentence that names the resource first and then the returned fields, with zero filler. Nothing could be cut without losing information.

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?

For a single-parameter read tool with no output schema, the description covers both what goes in (an Act) and what comes back (name, year, repeal status). Handling of an invalid or unsupported act_code is the only meaningful omission.

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?

There is a single parameter and schema description coverage is 100% – the schema already lists example codes and the count of supported Acts. The description adds no syntax, casing, or fallback 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get metadata about one specific Act') and enumerates what the metadata contains: full name, year enacted, and current/repealed status. This clearly separates it from list_acts and get_full_act, though it never names a sibling explicitly, so it stops 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for looking up a single Act's metadata, and 'one specific Act' hints it is not the bulk-listing tool. There is no explicit when-to-use guidance, no statement of when to prefer resolve_act or get_full_act instead, and no prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.