Skip to main content
Glama

Search AEC Knowledge

search_aec_knowledge
Read-onlyIdempotent

Search the Atlasly AEC knowledge graph: official data source registry, jurisdiction planning frameworks, technical standards, calculation tools, and domain records. kind=sources returns official datasets by jurisdiction. kind=jurisdictions returns policy frameworks (NPPF, NPF4, PPW, etc.). kind=standards returns technical standards (daylight, fire, acoustic, energy performance). kind=calculators returns calculation specs. Use verified_only=true to exclude unverified seed records. Unverified candidates are labelled and must not be cited as authoritative. To find which Atlasly tool to call, use search_tools instead. 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": "search_aec_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
debugNoInclude ranking/debug metadata in structured output
limitNo
queryNoSearch text, such as NPPF, daylight, fire, India, ADA, or U-value
top_kNo
countryNoOptional country/code filter, e.g. GB, US, England, Scotland
categoryNoOptional category/domain filter, e.g. planning, flood, heritage, ecology, transport, climate
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.
jurisdictionNoOptional country or jurisdiction filter
verified_onlyNoWhen true, return only official verified registry/dataset results
authority_levelNo
include_domainsNo
include_standardsNo
include_candidatesNoInclude unverified source candidates as labelled background context
include_calculatorsNo

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.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower; the description still adds real substance by disclosing that unverified seed records are labelled, included only via flags, and must not be cited as authoritative. It also explains the site_ref chaining contract. It doesn't mention result ranking, limits, or how 'all' composes with the include_* flags.

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?

Front-loaded with purpose, then a compact kind map, then the routing alternative and chaining contract — every sentence carries information. The four repeated 'kind=X returns...' clauses are slightly formulaic but each maps to a distinct enum value, so they are not filler.

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?

For a 15-param, multi-mode search with enumerated values and an output schema, the description covers mode selection, trust filtering, and cross-tool chaining. The main residual gap is that boolean include_* flags and their interaction with kind=all are not described.

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?

With 53% schema coverage across 15 params, the description compensates for the most consequential ones: the kind enum values are each explained, verified_only semantics are stated, and site_ref's chaining purpose is spelled out. It leaves limit, top_k, authority_level, and the include_* toggles unexplained, which is a real gap given the partial schema coverage.

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 (search) and resource (Atlasly AEC knowledge graph) and then enumerates the five result kinds with concrete examples (NPPF, NPF4, PPW, daylight, fire). It explicitly distinguishes itself from the sibling search_tools, which is the most likely confusion point.

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 per-kind routing guidance (kind=sources for datasets, kind=jurisdictions for policy frameworks, kind=standards for technical standards, kind=calculators for calc specs), a filter rule (verified_only=true), a restriction (unverified candidates must not be cited as authoritative), and an explicit alternative ('use search_tools instead').

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