Skip to main content
Glama

search_lexicons

Find ATProtocol lexicons by what their schemas say: descriptions, definition names, field names and known values. Use it when you don't know the NSID. mode "keyword" (default) matches words; mode "semantic" ranks by meaning, so a plain description of what you need works (e.g. 'store a user's reading list'), and it falls back to keyword when unavailable. By default only lexicons published by their NSID's DNS authority are returned. Returns NSIDs with summaries and AT-URIs; follow up with describe_lexicon.

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

Input Schema

NameRequiredDescriptionDefault
modeNokeyword (default) or semantic
limitNoMaximum results (default 10)
queryYesWhat to search for: words, a phrase in quotes, -word to exclude, or (with mode semantic) a plain description. 2 to 256 characters.
lexicon_typesNoOnly return lexicons whose main definition has one of these types
include_non_authoritativeNoAlso return lexicons whose publisher is not the NSID's DNS authority (default false). Such copies may be forks or impersonations.

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?

With no annotations, the description carries the burden well: it discloses the default trust filter (only DNS-authoritative publishers), the risk behind the opt-out (forks or impersonations), the semantic-to-keyword fallback, and the return shape (NSIDs with summaries and AT-URIs). It stops short of stating read-only safety, result ordering, or error behavior, which keeps it below 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?

Purpose is front-loaded in the first clause, then mode selection, then the trust default, then the return shape — a logical order with no filler. Every sentence carries information an agent would otherwise have to infer.

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

Completeness3/5

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

Mostly complete. It covers the 5-parameter surface, mode tradeoffs, the trust default, and return shape despite having no output schema. The main gap is the follow-up path: it says to call describe_lexicon next but not what input that call needs (the returned NSID).

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 the baseline is 3, but the description adds real meaning beyond it: what "semantic" actually does, that it degrades to keyword, that keyword is the default, and why include_non_authoritative matters. It does not add anything for limit, query syntax, or lexicon_types, which the schema already covers.

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 ("Find ATProtocol lexicons") plus the unusual search surface (schema contents: descriptions, definition names, field names, known values). The clause "Use it when you don't know the NSID" implicitly separates it from name/NSID-based siblings such as resolve_lexicon, and the follow-up pointer names describe_lexicon explicitly.

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 entry condition ("when you don't know the NSID"), explains the two modes with a concrete worked example for semantic mode, states the keyword fallback when semantic is unavailable, and prescribes the next step ("follow up with describe_lexicon"). The default authoritative-only behavior is also explained so the agent knows when to flip the flag.

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