Crossload

crossload_browse

List the topics, authors or series that exist in the catalogue, optionally filtered by a substring. Use it before filtering a search by topic, author or series: those filters need the exact name, and a guessed spelling returns nothing while the catalogue is in fact full. Topics carry their full path, which distinguishes identically named topics in different branches. For authors, 'detail' adds biography and picture when available.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	Which vocabulary to list.
`query`	No	Substring filter, e.g. 'verg' finds 'Vergebung'. Omit to get the full (capped) list.
`detail`	No	Only with kind='author'. Adds biography and picture when available. Use it to answer 'who is X' questions.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`status`	Yes
`entries`	Yes
`message`	No
`truncated`	No
`totalCount`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that results are capped, that topics carry full paths to disambiguate names, and that 'detail' adds biography/picture for authors. This is solid read-only behavioral context, though it does not discuss pagination or return shape, which the output schema may cover.

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?

Three tightly packed sentences with no filler. The core action is front-loaded, then usage guidance, then parameter-specific notes. Every sentence earns its place.

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?

For a simple browse/list tool with a full output schema and complete parameter descriptions, this is fully sufficient. It explains when to use it, what the quirks are, and how parameters behave.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds meaningful semantic context beyond the schema: a concrete example of substring matching, the disambiguation value of full topic paths, and the conditional behavior of 'detail' for authors only. This materially helps an agent use the parameters correctly.

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 ('List') and resource ('topics, authors or series'), with an optional substring filter. It also distinguishes itself from search filters by noting exact names are required for filtering, so an agent can tell this is the vocabulary-browsing tool.

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

Usage Guidelines4/5

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

Explicitly says to use this tool before filtering a search by topic, author, or series, and explains the exact-name requirement. It does not name sibling tools outright, but the usage guidance is clear and actionable.

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

All Crossload tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: browse resolves controlled vocabulary, search finds content items, read_content reads transcripts, lexicon looks up bible terms, and topic_stats aggregates counts. There is no real overlap or ambiguity between them.

Naming Consistency4/5

All tools share the crossload_ prefix and use snake_case, which makes the set feel consistent. The main deviation is that browse and search are bare verbs while read_content is verb_noun and lexicon/topic_stats are noun-style names, but the pattern is still easy to predict.

Tool Count5/5

Five tools is well-scoped for a retrieval-focused archive server. Every tool covers a distinct, necessary capability without redundancy or bloat.

Completeness4/5

The tool surface covers search, controlled-vocabulary lookup, transcript reading, term definition, and topic statistics, which is comprehensive for the domain. Minor gaps exist, such as no standalone metadata-by-uid retrieval and no way to locate a passage inside an item except by reading through it, but agents can work around these.

Resources

Need Help?