Skip to main content
Glama

Reunion India Real Estate

Compare observed RERA process references by state

compare_state_rera_processes
Read-onlyIdempotent

Compare a single RERA task across 2–6 Indian states using only currently observed source-backed records. Missing state/task data is not_observed_in_current_snapshot, not proof of absence.

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": {
      "states": "<states>",
      "task": "<task>"
    },
    "name": "compare_state_rera_processes"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
statesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value with the data-provenance caveat that missing state/task data appears as not_observed_in_current_snapshot rather than proving absence, but it says nothing about result shape, staleness windows, or snapshot recency.

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?

Two tight sentences, front-loaded with the core action and followed by the epistemic caveat; nothing is padded or redundant. The caveat sentence is slightly dense but earns its place as the tool's defining constraint.

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 two-parameter comparison tool with no output schema, the definition covers the action, the input boundaries, and the key interpretation caveat for missing data. It leaves only minor gaps, namely how states should be named and what the comparison payload looks like.

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 0%, so the description must carry the burden, and it does convey that 'task' is a single task per call and 'states' are Indian states bounded to 2–6. However, it does not clarify the enum values (e.g., project_bank, qpr_reporting, other) or the expected state-name format, leaving real ambiguity for an unconstrained string array.

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?

The description opens with a specific verb and resource ("Compare a single RERA task across 2–6 Indian states") and pins the scope, so an agent can immediately distinguish it from siblings like search_real_estate_regulations or get_rera_portal_capabilities without opening any schema.

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?

It states the operative context (compare one task across 2–6 states, using only currently observed source-backed records), which is enough to know when to reach for it. It stops short of naming alternatives or explicit exclusions, so it is clear context rather than full when/when-not guidance.

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