Skip to main content
Glama

Present Site Research

present_site_research
Read-onlyIdempotent

Purpose: present cited site research. When to use: after prepare_site_research and the host's own search, or to show unavailable search and gaps. Returns: Atlas AI UI, a JSON evidence register and a self-contained printable HTML pack. The HTML can be printed to PDF by the receiving browser; no generated or validated PDF is supplied. Parameter guidance: present up to 30 conversation-reported findings and 20 cited public HTTPS sources with dates, applicability, limitations and gaps. Every finding must reference a supplied unique source ID. Supply the previous site_ref unchanged. Limitations: this tool validates structure only; it does not fetch sources, confirm authority identity, verify facts/current law or establish parcel intersections. Empty evidence is unresolved, never no risk. Returns Atlas AI UI and JSON evidence register. Use publisher_kind authority_reported only as a reported classification; never label the result independently verified. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

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": {
      "question": "<question>",
      "sources": "<sources>",
      "findings": "<findings>",
      "gaps": "<gaps>"
    },
    "name": "present_site_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapsYes
addressNoSite address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations.
sourcesYes
findingsYes
questionYesThe user's question in their own words. It routes and labels the result; it is not answered as free text.
site_refNoCanonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted.
coordinatesNoUser-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified.
country_codeNoISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK.
radius_metersNoSearch radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected.

Output Schema

NameRequiredDescriptionDefault
queryNo
statusYes
detailsNo
messageNo
sourcesYes
headlineYes
site_refYes
retryableNo
error_codeNo
atlasly_linkYes
error_sourceNo
human_messageNo
key_data_pointsYes
top_constraintsYes
confidence_notesYes
executive_summaryYes
next_best_actionsYes
top_opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Site address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations."
    • addedInput schema / properties / coordinates / description
      Added value: +"User-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified."
    • addedInput schema / properties / country_code / description
      Added value: +"ISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK."
    • addedInput schema / properties / question / description
      Added value: +"The user's question in their own words. It routes and labels the result; it is not answered as free text."
    • addedInput schema / properties / radius_meters / description
      Added value: +"Search radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag readOnly/idempotent/non-destructive, yet the description goes well beyond them: it discloses that validation is structural only, that no sources are fetched, authority/facts/current law are unverified, empty evidence means unresolved rather than 'no risk', and that publisher_kind=authority_reported is a reported classification only. It also warns that no generated or validated PDF is produced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading with Purpose/When to use/Returns/Limitations/Chaining labels is good structure, but the text repeats itself: 'Returns Atlas AI UI and JSON evidence register' appears twice and the HTML/PDF disclaimer is restated in two places. Trimming the duplicate sentences would sharpen it without losing information.

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

Completeness5/5

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

For a 9-parameter nested-schema tool with an output schema and full annotation coverage, the description covers invocation preconditions, data-integrity constraints, epistemic limitations, and chaining. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 67%, and the description compensates with referential-integrity rules not expressible in the schema ('every finding must reference a supplied unique source ID') and the requirement to 'supply the previous site_ref unchanged'. It does not explain radius_meters, coordinates, or country_code behavior, leaving the remaining uncovered params to the schema field descriptions.

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?

States a specific verb and resource ('present cited site research') and immediately delimits the output artifacts (Atlas AI UI, JSON evidence register, printable HTML pack). It also implicitly separates itself from the sibling prepare_site_research by positioning itself as the downstream presentation step.

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

Usage Guidelines5/5

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

The 'When to use' sentence names both the precondition (after prepare_site_research and the host's own search) and the fallback case (to show unavailable search and gaps). The Chaining sentence tells the agent exactly how to reuse site_ref in subsequent Atlasly calls.

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