Skip to main content
Glama

Get Official Source Adapters

get_official_source_adapters
Read-onlyIdempotent

List Atlasly registered official-source adapters for USA/EU/global site intelligence. Use to inspect source endpoint readiness, token requirements, and health-check queue instructions before relying on unsupported-location research. Omit every filter to list all registered adapters. For UK local planning authority adapters, use get_lpa_adapter_status. 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

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

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNoCountry or region code, e.g. US or EU
categoryNoCategory such as flood, terrain, heritage, environment, transport, source-discovery, jurisdiction
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.
source_keyNoSource registry key
adapter_keyNoSpecific adapter key
dataset_keyNoSingle Atlas dataset key
dataset_keysNoAtlas dataset keys to inspect

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. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered. The description adds context the annotations cannot: what the records contain (endpoint readiness, token requirements, health-check queue instructions) and the cross-tool chaining contract via site_ref. It does not discuss rate limits, pagination, or ordering of the limited list.

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?

Purpose and use case are front-loaded, then the default, then the sibling exclusion, then chaining. Four dense sentences with little waste, though the trailing chaining sentence is generic boilerplate that recurs across the toolset and could be trimmed.

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?

An output schema exists so return values need not be enumerated, and annotations cover safety and idempotency. For an 8-parameter, zero-required, read-only discovery tool, the description supplies everything an agent needs to decide to call it and how filters behave, including the chaining handoff.

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 description coverage is 88% and the schema already documents country, category, source_key, adapter_key, and the site_ref chaining object, so the baseline is 3. The description adds one genuine semantic beyond the schema: omitting all filters returns every registered adapter, which tells the agent the filters are conjunctive narrowing rather than required selectors.

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 ('List Atlasly registered official-source adapters') with a clear scope ('USA/EU/global site intelligence'), and explicitly excludes the UK LPA case in favor of a named sibling. An agent can distinguish this from get_lpa_adapter_status without opening either schema.

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?

Gives the motivating use case ('inspect source endpoint readiness, token requirements, and health-check queue instructions before relying on unsupported-location research'), the default behavior when no filters are supplied, and the explicit alternative plus its selection condition (UK local planning authority → get_lpa_adapter_status).

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