A2UI Atomic Catalog

find_atoms

Read-onlyIdempotent

Semantic search over the atom catalog: describe the UI piece you need in plain words and get the best-matching atoms, ranked best-first, each with a description and an example need. YOU choose from the list (the first entries are most likely, but check the descriptions), then call get_atom_schema for the one(s) you pick. Use this instead of scanning get_catalog when the vocabulary is large. Describe the need as a user would (e.g. "let clients choose grooming services and see the total price"), not by guessing an atom name.

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": {
      "need": "<need>"
    },
    "name": "find_atoms"
  }
}

Input Schema

Name	Required	Description	Default
`k`	No	How many candidates to return (default 10, max 50). If none fits, rephrase the need or ask for more.
`need`	Yes	The UI piece you need, in plain words (one need per call)

Output Schema

Name	Required	Description
`atoms`	Yes	Candidates, best first.
`count`	Yes	Number of ranked atoms returned.
`confident`	Yes	True when the best score clears the rejection floor.
`also_named`	No	Unranked atoms whose names share a word with the request.
`also_named_note`	No	Why also_named is listed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses the ranking semantics, what each result contains (description plus example need), and that the agent must make the final selection. It does not state match-quality or latency characteristics, which keeps it short of a 5 for an open-world search.

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?

Four sentences, front-loaded with the search purpose and workflow before caveats; there is minor overlap between "YOU choose from the list" and the note that the first entries are most likely. No filler or boilerplate.

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 no explanation, and the description still covers the selection workflow, phrasing guidance, and the no-fit fallback. 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%, so baseline is 3, but the description adds real meaning: the need should be phrased in user language rather than as a guessed atom name, and the ranking means the first entries are most likely. That is guidance the schema does not carry.

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 ("semantic search over the atom catalog") plus the input form (plain-words need) and output shape (best-matching atoms ranked best-first). It explicitly contrasts with sibling get_catalog, so an agent can pick between them without opening a 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 explicit routing: use this instead of scanning get_catalog when the vocabulary is large, then call get_atom_schema on the picks. It also specifies the input style (describe the need as a user would, not by guessing an atom name) and a fallback (rephrase or ask for more if nothing fits).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All A2UI Atomic Catalog tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.