Skip to main content
Glama

Lexicon Garden

Server Details

Resolve, search, and validate AT Protocol lexicons.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clear, distinct jobs: search finds NSIDs, discover_permission_sets handles OAuth scopes, validate checks correctness, and check_compatibility compares two versions. The one soft boundary is resolve_lexicon vs describe_lexicon, since both fetch a schema by NSID; the descriptions hint resolve is for retrieval/provenance and describe is for structural detail, but an agent could plausibly pick either.

Naming Consistency5/5

Every tool follows a strict snake_case verb_noun pattern (check_compatibility, describe_lexicon, discover_permission_sets, resolve_lexicon, search_lexicons, validate_lexicon). The leading verb accurately signals the operation type across the whole set.

Tool Count5/5

Six tools is well-scoped for a lexicon registry: discovery, retrieval, inspection, validation, version compatibility, and permission-set lookup. No tool appears redundant or padded, and nothing feels conspicuously absent from the count.

Completeness4/5

The read/analysis lifecycle is well covered end to end: find, resolve, describe, validate, diff versions, and map to OAuth scopes. Gaps are minor and arguably intentional for a read-only index — there is no way to publish/create a lexicon or enumerate all lexicons under a given authority, but agents can work around these via search and resolve.

Available Tools

6 tools
check_compatibilityAInspect

Check compatibility between two versions of an ATProtocol lexicon schema. Detects breaking vs non-breaking changes and provides migration guidance. Supply either two schema JSON objects directly (from_schema + to_schema), or an NSID with two CIDs to compare stored versions (nsid + from_cid + to_cid).

Inputs: nsid, to_cid, from_cid, to_schema, +1 more.

describe_lexiconAInspect

Get detailed information about an ATProtocol lexicon schema: its definitions, authority, CID and any published documentation. Use this to understand the structure and format of XRPC methods, records, and other lexicon types.

Inputs: lexicon (required), identity, language.

discover_permission_setsAInspect

Discover which ATProtocol permission-set lexicon schemas cover a given set of collections and/or XRPC methods. Returns matching permission sets with their OAuth scope strings (include:<nsid>), useful for determining what OAuth scopes an application needs.

Inputs: collections (required), methods.

resolve_lexiconAInspect

Resolve an ATProtocol lexicon by NSID: find the DID named by the _lexicon TXT record of the NSID's authority and read that DID's com.atproto.lexicon.schema record, from Lexicon Garden's index or, when it is not indexed or refresh is set, from the network. Returns the schema, its AT-URI and CID, the authority DID and where it came from.

Inputs: nsid (required), refresh.

search_lexiconsAInspect

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.

Inputs: query (required), mode, limit, lexicon_types, +1 more.

validate_lexiconAInspect

Validate a lexicon schema and optionally validate data against it. Use this to verify schema correctness and validate records, query params, or procedure inputs against their schemas.

Inputs: schema (required), flags, input, params, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes a version-controlled knowledge base as MCP tools so agents can read merged identity/state summaries and next recommended actions at runtime, plus run deterministic schema validation and cross-reference link checks. This lets agents fetch live state and verify integrity via self-describing calls instead of re-reading raw files.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Lets coding agents search locally captured product UI reference packs — including extracted design tokens and per-screen OCR text — plus licensed font families, icon sets, and Lottie animations, returning absolute on-disk paths with source and license info. Everything is served from local storage with no registration, tokens, or network access at query time.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to a local-first catalog of portable agent skills, exposing tools to discover ranked matches, inspect stored artifacts, traverse declared relationships, and view configuration.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to search, resolve and audit DTCG design tokens — finding the token behind an intent or a hard-coded color/size, checking naming grammar, auditing CSS for hard-coded or unknown tokens, arbitrating semver, and previewing token additions as JSON Patch diffs. Writes are gated behind explicit confirmation plus an opt-in flag, so every change arrives as a reviewable proposal rather than an edit.
      7
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources