Skip to main content
Glama
Sign In
Helios

Helios

by brazaoo4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

manage_scope_alias

Destructive

Map project aliases to canonical scopes and migrate stored memories when renaming projects; list aliases or remove mappings without deleting memories.

Instructions

Manage project alias mappings and migrate memory scopes in SQLite. action='list' is read-only and returns all aliases plus per-scope active/stale counts; action='set' maps alias to canonical_scope; action='remove' deletes only the alias mapping while leaving stored memories untouched; action='rename' destructively migrates all memories from alias into canonical_scope, registers the alias, and syncs Markdown exports. 'set' and 'rename' require both alias and canonical_scope, while 'remove' requires alias. Use manage_scope_alias to unify repository names or rename projects; use manage_server_config for server tunables or distill_memories to clean up memories within a scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manage_scope_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasNoSource alias or folder name (e.g., 'ticket-tracker').
actionNoAction to perform: 'set' (map alias), 'remove' (delete alias), 'list' (show all), or 'rename' (migrate all memories to new scope and register alias).set
canonical_scopeNoTarget canonical scope name (e.g., 'ticketera').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations collapse the whole tool into destructiveHint=true, but the description disaggregates that: 'list' is read-only, 'remove' deletes only the mapping and leaves memories untouched, and 'rename' destructively migrates all memories and syncs Markdown exports. This is material behavioral context an agent cannot derive from the annotations, and it is consistent with them rather than contradicting them.

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?

Front-loaded with purpose and then structured action-by-action, with the sibling routing last. It is dense and sentence two is a long semicolon chain, but nearly every clause carries operative information, so it is efficient rather than padded.

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?

With an output schema present, the description needn't explain return payloads, yet it still notes that 'list' returns aliases plus per-scope active/stale counts. Combined with per-action side effects and prerequisite parameters, an agent has everything needed to call the tool correctly and safely.

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

Parameters4/5

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

Schema coverage is 100%, so the field meanings are already documented, but the schema declares zero required parameters while the description supplies the conditional requirements per action – real added value the schema lacks. It does not add much beyond that (e.g., what a canonical_scope must look like, or how stale counts are computed), so it stops short of a 5.

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+resource ('Manage project alias mappings and migrate memory scopes in SQLite') and then enumerates exactly what each of the four actions does, so an agent can select the right action without opening the schema. It is also clearly distinguished from siblings by naming manage_server_config and distill_memories as adjacent-but-different tools.

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

Usage Guidelines5/5

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

Gives explicit usage routing: 'use manage_scope_alias to unify repository names or rename projects; use manage_server_config for server tunables or distill_memories to clean up memories within a scope.' It also states per-action parameter requirements ('set' and 'rename' require both alias and canonical_scope, 'remove' requires alias), which is exactly the guidance an agent needs before calling.

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

Deploy Server

Other Tools