Skip to main content
Glama
RandomSynergy17

Arcane MCP Server

List registries

arcane_registry_list
Read-onlyIdempotent

List configured container registries with search and pagination options.

Instructions

List configured container registries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch query
startNoPagination start
limitNoItems per page
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, indicating a safe read operation. The description does not add behavioral context beyond that, such as pagination or sorting behavior.

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 a single sentence with no unnecessary words. It is focused and concise.

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 simple list operation with no output schema, the description adequately states the purpose. However, it could specify that it returns a list of registry objects, which is implied by 'list'.

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?

All three parameters (search, start, limit) have descriptions in the input schema (100% coverage). The description adds no extra meaning beyond what the schema already provides.

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 title 'List registries' and description 'List configured container registries' clearly state the action and resource. It distinguishes from sibling tools like arcane_registry_create, delete, get, sync, test, update, which have different verbs.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The purpose is implied as a simple listing operation, but there is no comparison with arcane_registry_get for fetching a single registry.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RandomSynergy17/Arcane-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server