Skip to main content
Glama
Sign In
Mirsad

Mirsad

by amkkoussay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_alias

Registers an alternate name, spelling, or script for an entity so future lookups under that alias resolve to the same entity.

Instructions

Register another name for an entity (another language, spelling or script) so future lookups in that name resolve to the same entity.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": "<entity>",
      "alias": "<alias>"
    },
    "name": "add_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYes
entityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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. It does disclose the persisted effect of the call (aliases resolve on future lookups), but omits what happens on a conflicting or duplicate alias, whether an existing alias can be replaced, and whether errors are raised if the entity is unknown.

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?

One tight sentence with the action first and the rationale in a trailing purpose clause; nothing is redundant or padded.

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 two-parameter write tool with no annotations and no output schema, the description covers the action, the input meaning of alias, and the observable effect. The remaining gap — what entity refers to and how duplicate aliases are handled — is minor but not trivial for a mutation tool.

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?

Schema coverage is 0%, so both parameters rely on their names alone. The description adds real meaning for "alias" (other language, spelling or script) but leaves "entity" undefined — the agent cannot tell whether it expects an internal ID, a canonical name, or a free-form reference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ("register") applied to a specific resource (another name for an entity), with the effect spelled out. It is clearly distinct from the memory/recall siblings, though it does not name any sibling explicitly.

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?

The clause "so future lookups in that name resolve to the same entity" implies the situation that calls for this tool, but there is no explicit when-not guidance, no mention of alternatives, and no prerequisites such as whether the entity must already exist.

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