Skip to main content
Glama

Search Tools

search_tools
Read-onlyIdempotent

Discover available Atlasly tools by keyword. Call this first when unsure which tool to use. Returns tool names, one-line summaries, and required parameters. To search standards, policy frameworks or official datasets, use search_aec_knowledge 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

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": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword to search: e.g. flood, planning, walkability, topography, precedents, transit
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.

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

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description adds genuine value by disclosing the response shape (tool names, one-line summaries, required parameters) and the site_ref chaining contract that carries site, coordinates, boundary confidence, LPA and evidence links forward. It stops short of stating result limits or ranking behavior, so not 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.

Conciseness5/5

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

Four sentences, front-loaded with the purpose, then the trigger, then the exclusion, then the chaining contract. No filler, no restatement of the title, and the highest-value routing information (call first / use sibling instead) comes before the mechanics.

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?

Complete for a discovery tool: an output schema exists so return values needn't be enumerated, yet the description still summarizes them, and the chaining protocol — the one behavior an agent could get wrong — is spelled out. Nothing needed to call this 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 100% and the query parameter already has keyword examples, so the baseline is 3; the description earns above baseline by explaining what site_ref does semantically — pass it unchanged to reuse the canonical site and project context. It does not restate the required fields inside site_ref, but the nested schema description already does that.

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 ("Discover available Atlasly tools by keyword") and immediately names the adjacent-but-different sibling (search_aec_knowledge for standards/policy/datasets). An agent can distinguish this meta-discovery tool from the ~30 domain tools without opening any 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 an explicit trigger ("Call this first when unsure which tool to use") and an explicit exclusion with the alternative named ("To search standards, policy frameworks or official datasets, use search_aec_knowledge instead"). This is the when/when-not/alternative pattern done fully.

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