Skip to main content
Glama

alias_pattern

Merge duplicate patterns in AI memory by redirecting observations from one pattern to another, consolidating confidence without data loss.

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

Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining key behaviors: future observations are rerouted silently, existing confidence is summed into the target, and failure conditions (target missing) with error response format. It doesn't mention rate limits or auth needs, but covers core operational traits adequately.

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?

The description is well-structured with clear sections (purpose, usage, args, returns) and every sentence adds value. It could be slightly more concise in the opening paragraph but remains efficient overall with no wasted text.

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 2 parameters with no schema descriptions, no annotations, but with output schema details provided, the description is complete. It covers purpose, usage, parameters, return values, and error conditions, providing everything needed for an agent to use this tool correctly.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters thoroughly: 'pattern' is 'the key to retire' and 'target' is 'the canonical key to absorb into' that 'must already exist in the store'. It adds meaningful context beyond the bare schema types.

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 purpose with specific verbs ('redirect', 'merge duplicates') and resources ('pattern', 'key'), distinguishing it from siblings like 'find_duplicates' which only discovers candidates. It explains the core function of aliasing one pattern to another to consolidate data.

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?

The description provides explicit guidance on when to use this tool: to merge duplicates discovered by 'find_duplicates()', with the target pattern already existing. It also specifies prerequisites ('target must already exist') and distinguishes from alternatives by referencing the sibling tool for discovery.

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/yakuphanycl/instinct'

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