Skip to main content
Glama

Reunion India Real Estate

Get observed RERA portal capabilities

get_rera_portal_capabilities
Read-onlyIdempotent

Return observed official RERA portal capability links. Missing rows mean not observed in the current snapshot, not that a capability does not exist.

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_rera_portal_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
limitNo
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real value beyond them by disclosing snapshot semantics: missing rows mean 'not observed in the current snapshot,' which prevents an agent from treating an empty result as proof a capability does not exist. It still omits result shape, snapshot freshness, and how limit/truncation behaves.

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?

Two sentences with no waste; the core action is front-loaded and the caveat follows immediately. Nothing is repeated and no filler appears.

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 three-parameter, filter-driven lookup with no output schema and no annotation coverage of data semantics, the description should say at least roughly what a returned capability record contains and how task/state/limit shape the result. The snapshot caveat is helpful but the parameter behavior and return contents are entirely undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for three parameters, and it explains none of them. The nine-value task enum, the state filter, and the limit cap (default 10, max 20) are all left for the agent to guess at, which matters because these parameters define what the response can cover.

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: 'Return observed official RERA portal capability links.' The qualifier 'observed' is meaningful and the scope is clear. It does not, however, distinguish itself from siblings such as get_source_provenance or compare_state_rera_processes, 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 Guidelines2/5

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

There is no guidance on when to call this versus alternatives, and no prerequisites or exclusions. The second sentence is an interpretive caveat about absent rows, not a routing rule, so an agent must infer the use case from the purpose statement alone.

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