Skip to main content
Glama

alias_pattern

Redirect future observations of a pattern to another key. Merge duplicate patterns by aliasing a stray key to an existing canonical key, summing confidence into the target.

Instructions

Redirect all future observations of one pattern onto another.

    Use this to merge duplicates: when the same concept has been recorded
    under two keys (e.g. "seq:a->b" and "seq:a -> b" with a space), alias
    the stray into the canonical one. Existing confidence is summed into
    the target so no learning is lost.

    The target must already exist. Use find_duplicates() to discover
    merge candidates, then call this to apply them.

    Args:
        pattern: The key to retire. Future observations of this key will
            be rerouted silently.
        target: The canonical key to absorb into. Must already exist in
            the store.

    Returns:
        On success: {"aliased": <pattern>, "target": <target>}.
        On failure (target missing): {"error": "target pattern '<target>'
        not found"} — check for the "error" key.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYes
targetYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes side effects (future observations rerouted silently, confidence summed), error condition, and return format. No annotations provided, but description fully compensates.

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?

Well-structured with sections, but slightly verbose in docstring style. Could be more concise without losing clarity.

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?

Covers purpose, usage, parameters, return values, and error handling. Even references a sibling tool for discovery. Complete for a non-trivial merge operation.

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 0%, but description provides clear semantics for both parameters: pattern as key to retire, target as canonical key to absorb into.

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?

Clear verb 'alias' and resource 'pattern', with specific use case of merging duplicates. Differentiates from sibling tools by explicitly mentioning companion find_duplicates.

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?

Explicitly states when to use (merge duplicates), prerequisite (target must exist), and suggests find_duplicates to discover candidates.

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/WRG-11/instinct'

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