Skip to main content
Glama

Reunion India Real Estate

Get observed RERA regulatory change history

get_regulatory_change_history
Read-onlyIdempotent

Return observed official RERA notices and circulars. The feed is partial and preserves official publication dates only when exposed by the authority index.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_regulatory_change_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo
topicsNo
to_dateNo
from_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful caveats that the feed is partial and preserves official publication dates only when exposed by the authority index, but it omits ordering, pagination, and completeness behavior beyond 'partial.'

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?

The description is two short, front-loaded sentences with no filler. It is efficiently written, though its brevity contributes to the under-specification of parameters and usage.

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

Completeness2/5

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

For a tool with five undocumented parameters and no output schema, the description is too thin. It establishes the high-level purpose and a partial-feed caveat, but it does not explain filtering, result ordering, or how to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for five parameters, including state, topics, limit, from_date, and to_date. The description never explains what these filters do, how they interact, or that topics accepts a fixed enum; the brief mention of publication dates does not compensate for missing parameter semantics.

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?

The description uses a specific verb and resource: 'Return observed official RERA notices and circulars.' This makes the tool's output clear enough to distinguish from a generic search, though it does not explicitly differentiate itself from siblings such as search_real_estate_regulations.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no exclusions, and no alternatives. A reader can infer it is for regulatory notice history, but there is no guidance on when to choose this over sibling research or search tools.

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.

Resources