Skip to main content
Glama
informatics-isi-edu

Deriva MCP Server

Official

create_catalog_alias

Create a memorable alias for an existing catalog, enabling access via a custom name instead of numeric ID.

Instructions

Create an alias for an existing catalog.

Aliases allow accessing a catalog by a memorable name instead of its numeric ID. For example, instead of /ermrest/catalog/21, you can use /ermrest/catalog/eye-ai.

Args: hostname: Server hostname (e.g., "www.eye-ai.org"). alias_name: The alias identifier (e.g., "my-project", "eye-ai"). Must be unique on the server. catalog_id: The numeric ID of the catalog to alias. name: Optional display name for the alias. description: Optional description of the alias.

Returns: JSON with status and alias details.

Example: create_catalog_alias("localhost", "my-project", "45", "My ML Project") -> {"status": "created", "alias": "my-project", "target": "45"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
hostnameYes
alias_nameYes
catalog_idYes
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral transparency. It discloses the uniqueness requirement for alias_name, the purpose of aliases, and the return format with an example, which gives good context for expected 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 well-organized with Args, Returns, and Example sections, making it scannable. Every sentence provides useful information, and the example clarifies the expected input/output.

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?

The description covers the purpose, all parameters, the return value, and includes a concrete example, which is sufficient for an agent to select and invoke this tool correctly. The sibling list provides context for related operations, though the description does not need to mention them.

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?

The schema provides no descriptions for any of the 5 parameters (0% coverage), but the description compensates with an Args section that explains each parameter, including the format for hostname, the uniqueness constraint for alias_name, and the numeric nature of catalog_id.

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's function ('Create an alias for an existing catalog') and explains the benefit of using aliases with a concrete example. It distinguishes from sibling tools like update_catalog_alias and delete_catalog_alias by explicitly focusing on creation.

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?

The description provides clear context for when to use this tool: when a user wants to create a memorable alias for a numeric catalog ID. It includes an example invocation, but does not explicitly mention when not to use it or recommend alternatives such as update_catalog_alias.

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/informatics-isi-edu/deriva-mcp'

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