Remember Me Collections

browse_collections

Read-onlyIdempotent

Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity.

Each result includes the collection's raw cover image — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image.

Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No
`language`	No
`ordering`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context about the raw image field being the stored publisher URL (or null) rather than a computed display image, which is a non-obvious behavioral detail. This goes beyond what annotations provide.

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?

The description is structured with a clear summary sentence, a useful behavioral note about the image field, and a compact bullet-style Args list. Every sentence earns its place without unnecessary verbosity.

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?

Given the output schema exists, no return format explanation is needed. The description covers tool purpose, parameter semantics, result nuance, and default behavior. It is fully self-contained for a browse/list tool.

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?

Despite 0% schema description coverage, the description fully explains all 5 parameters: search term scope, language code prefix, ordering options with default, limit range (1-100 default 20), and offset for pagination. This compensates completely for the schema's lack of descriptions.

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?

The description clearly states the tool browses published Bible verse collections, with specific verbs 'browse', 'search', 'filter', and 'sort'. It distinguishes from siblings (get_collection_detail, get_collection_metrics) by focusing on list-level browsing rather than detail or metrics.

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?

Provides clear context for when to use the tool: searching/filtering/sorting collections. It does not explicitly exclude alternatives, but sibling names imply browse is for list operations vs detail/metrics. Default ordering and parameter behavior offer practical usage guidance.

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

All Remember Me Collections 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.3/5.0

Disambiguation5/5

Each tool targets a distinct aspect: browse_collections for searching and listing, get_collection_detail for full content of a single collection, and get_collection_metrics for engagement statistics. There is no functional overlap, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: browse_collections, get_collection_detail, get_collection_metrics. The naming is predictable and clear, with no mixed conventions or vague verbs.

Tool Count4/5

With only 3 tools, the server is lean but well-scoped for a read-only collections browser. Each tool serves an essential purpose, though the small count might feel slightly thin for broader use cases.

Completeness4/5

The server covers the core read-only workflow: search/browse, retrieve full details, and access metrics. Missing create/update/delete operations, but these appear out of scope given the 'published collections' focus.

Resources

Need Help?