Skip to main content
Glama
Vaquill-AI

Vaquill-AI/vaquill-mcp

Official

list_legislation

Find act IDs for Indian legislation by browsing 23,000+ acts, with filters for category, state, department, year, and status.

Instructions

Browse 23,000+ Indian acts, regulations, and legislation. Use to discover act_id values for get_act_text and get_amendments. Filter by category (central, state, regulatory, repealed, spent), state slug, department (sebi, rbi, etc.), year range, and status (in_force, repealed, spent). Sort by year_desc, year_asc, title_asc, title_desc, or popular. Cost: 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter: central, state, regulatory, repealed, spent
stateNoFilter by state slug (e.g. 'maharashtra', 'delhi')
departmentNoFilter by regulatory body (e.g. 'sebi', 'rbi')
yearFromNoMinimum year (inclusive)
yearToNoMaximum year (inclusive)
statusNoFilter: in_force, repealed, spent
searchNoFilter by title substring
sortNoSort: year_desc, year_asc, title_asc, title_desc, popularyear_desc
pageNoPage number
pageSizeNoResults per page (1-100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description partially covers behavior: notes cost (1 credit) and implies read-only ('browse'), but lacks details on pagination limits, rate limiting, or output structure count.

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?

Three sentences with front-loaded purpose, no fluff, and efficient coverage of key usage and filters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although it covers main filters, it omits mention of the search parameter (substring filtering) and does not differentiate from search_legislation; output schema exists but pagination details are missing in description.

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%; description summarizes filters but adds no new meaning beyond what the schema already provides (e.g., listing categories, sorts).

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?

Description clearly states the tool browses 23,000+ Indian acts and is used to discover act_id values for get_act_text and get_amendments, distinguishing it from sibling tools.

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 (discover act_id), and hints at downstream tools, but does not explicitly exclude use for full-text search or compare with search_legislation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vaquill-AI/vaquill-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server