Skip to main content
Glama

Lexicon Garden

resolve_lexicon

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.

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": {
      "nsid": "<nsid>"
    },
    "name": "resolve_lexicon"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsidYesThe NSID to resolve (e.g., 'app.bsky.feed.post')
refreshNoOptional: read the record from the network even when it is indexed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the data source hierarchy (Lexicon Garden index vs. live network), what triggers the network path, and exactly what is returned (schema, AT-URI, CID, authority DID, provenance). What it omits is failure behavior — what happens when the NSID has no `_lexicon` TXT record, the DID lacks the schema record, or the network fetch fails.

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?

A single front-loaded sentence that starts with the verb and resource, with the mechanism and return values following in logical order. It is dense — the parenthetical fallback clause and the return-value list could be split for readability — but no sentence is wasted.

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?

For a two-parameter read operation with no output schema, the description covers source selection, return shape, and provenance, which is most of what an agent needs. The main missing piece is error/empty-result behavior, plus any hint of latency or rate limits when hitting the network path.

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 the schema already documents both `nsid` (with an example) and `refresh`. The description reinforces `refresh` by tying it to the index-vs-network branch, which adds a little context, but it adds no format or syntax detail beyond the schema. 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?

The description gives a specific verb ('Resolve') and resource ('ATProtocol lexicon by NSID') and even spells out the resolution mechanism: the authority's `_lexicon` TXT record, then that DID's com.atproto.lexicon.schema record. That makes the operation clearly a fetch/resolve, distinguishable in practice from validate_lexicon or describe_lexicon, though no sibling is named explicitly.

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?

Usage is only implied by the operation itself — you call it when you need the schema record for a known NSID. There is no explicit statement of when to prefer this over search_lexicons (to find NSIDs) or describe_lexicon/validate_lexicon, and no prerequisites or exclusions are given. The note about 'when it is not indexed or refresh is set' describes internal fallback logic, not tool selection.

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