Skip to main content
Glama

Reunion India Real Estate

Get observed project-bank and QPR references

get_project_bank_qpr_requirements
Read-onlyIdempotent

Return observed source-backed RERA references classified as project-bank and/or quarterly-progress-reporting material. Verify the linked authority source before acting.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo
topicNoboth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the data is 'observed' rather than authoritative, it is 'source-backed', and the agent is told to verify the linked authority source before acting on it. That provenance caveat is the most valuable information here and is not present in any structured field. It does not mention result volume or how the limit bounds output, which keeps it from a 5.

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 sentences, front-loaded with the resource description and ending with the most actionable instruction. No filler or repetition. It is arguably too terse given the undocumented parameters, but on the conciseness dimension itself it is efficient and well-ordered.

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?

With no output schema, the description should convey what an 'observed reference' record contains and how results are shaped, but it does not. Combined with 0% parameter documentation and no guidance on selecting this tool versus its siblings, an agent can form only a rough picture of the call. The verification instruction is the sole piece of operational context provided.

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% across three parameters, so the description carries the full burden and largely drops it. It never explains what 'state' expects (a name, a code, a jurisdiction), that 'limit' caps result count with a maximum of 20, or how 'topic' resolves to project-bank versus QPR versus both. The enum values and defaults are self-explanatory in the schema, which yields a small amount of meaning, but the description adds nothing to compensate for the coverage gap.

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 names a specific verb ('Return') and a specific resource ('observed source-backed RERA references'), then narrows it to two named categories: project-bank and quarterly-progress-reporting material. An agent knows exactly what this tool retrieves. It does not, however, distinguish itself from siblings like get_source_provenance or search_real_estate_regulations, so it falls 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 explicit statement of when to choose this tool over the sibling tools, nor any when-not or prerequisite guidance. The single clause 'Verify the linked authority source before acting' is a downstream caution about how to use the results, not guidance on when this tool is the right selection. An agent must infer its usage context from the resource name 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