Skip to main content
Glama

Lexicon Garden

describe_lexicon

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.

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": {
      "lexicon": "<lexicon>"
    },
    "name": "describe_lexicon"
  }
}

Input Schema

NameRequiredDescriptionDefault
lexiconYesThe lexicon NSID to describe (e.g., 'app.bsky.feed.post', 'com.atproto.repo.createRecord', or 'app.bsky.actor.profile#viewBasic' for a specific fragment)
identityNoOptional: The identity (DID like 'did:plc:...' or handle like 'alice.bsky.social') of the authority publishing this lexicon. If not provided, the authority will be resolved via DNS.
languageNoOptional: Preferred language code (ISO 639) for localized descriptions from garden.lexicon.documentation records. If not provided, only schema descriptions are shown. Use language codes like 'en', 'pt-BR', 'ja', etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose useful behavior: the identity parameter falls back to DNS resolution, and localization comes from garden.lexicon.documentation records. It stops short of stating failure behavior for unknown NSIDs, whether results are cached, or any rate limits — notable for a network-backed lookup.

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?

Two sentences, front-loaded with the return payload before the usage note. Nothing is wasted, though the second sentence is fairly generic and could have been spent on tighter differentiation from sibling tools.

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?

There is no output schema, so the enumeration of returned fields (definitions, authority, CID, documentation) is valuable and largely fills that gap. For a read-only lookup with fully documented parameters, this is close to complete; only error and edge-case behavior is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters including the NSID-fragment syntax and DNS fallback are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Get detailed information') plus resource ('ATProtocol lexicon schema') and enumerates the payload: definitions, authority, CID, published documentation. An agent knows exactly what comes back. It does not, however, distinguish itself from siblings such as resolve_lexicon or validate_lexicon, which sound adjacent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives a usage context ('to understand the structure and format of XRPC methods, records, and other lexicon types'), which is real but generic. There is no when-not guidance, no prerequisites, and no named alternative for the resolve/validate-style tasks that sibling tools likely cover.

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