Skip to main content
Glama

Reunion India Real Estate

Get exact source provenance for a Reunion MCP record

get_source_provenance
Read-onlyIdempotent

Return official source URL, observation time, source-page SHA-256 and extraction locators for one record ID. Does not expose private storage keys or raw crawl bodies.

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": {
      "record_id": "<record_id>"
    },
    "name": "get_source_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety bar is low. The description still earns credit for disclosing the negative space of the output — no private storage keys, no raw crawl bodies — which tells an agent what it may safely surface. It says nothing about behavior for an unknown record ID or any access constraints.

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, both front-loaded: the return payload first, the exposure boundary second. No filler, no restatement of the tool name, nothing that could be cut.

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?

There is no output schema, so the description correctly carries the burden of naming the returned fields (URL, observation time, SHA-256, locators), which is what an agent needs to decide whether this is the right citation source. It falls short only on record-ID acquisition and error behavior for missing records.

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% for the single parameter; the only structure is a 24-hex-character pattern. The description merely restates "one record ID" and adds no meaning about format, where IDs come from, or whether it accepts batch input, so it does not 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?

"Return official source URL, observation time, source-page SHA-256 and extraction locators for one record ID" gives a specific verb plus a concrete, enumerated set of returned fields and a scope of exactly one record. It is clearly distinct in subject matter from the listed siblings (regulatory/portal lookups), though it does not explicitly name a sibling to contrast against.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the provenance/citation tool for a single known record, but there is no statement of when to prefer it over siblings, no prerequisite (e.g. having obtained a record ID from a search tool), and no exclusion or failure case.

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