Skip to main content
Glama
Sign In
@zeph-to/mcp-server

@zeph-to/mcp-server

by zeph-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zeph_session_rename

Rename the current agent session with a custom label to identify it among parallel sessions in the Zeph app. Set a display name for clarity and organization.

Instructions

Set a custom display name for THIS agent session in the user's Zeph app (the Streams › Agents list). Label what this session is working on — e.g. "Prod deploy" or "Auth refactor" — so the user can tell parallel sessions apart on their phone. Renames the current session; the name persists until changed.

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": {
      "alias": "<alias>"
    },
    "name": "zeph_session_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYesDisplay name for this session (max 60 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate a non-read-only, open-world, non-destructive operation. The description adds context that the rename persists until changed and targets 'THIS agent session' specifically, making the side effects clear. This goes beyond simply restating the annotations.

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 three sentences with no fluff. The first sentence states the action, the second provides usage guidance with examples, and the third clarifies persistence. Every sentence earns its place.

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?

For a simple tool with one parameter, no output schema, and helpful annotations, the description fully covers the action, the context of use, and the durability of the change. There are no missing details that would cause an agent to misuse the tool.

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?

The schema already covers the single parameter 'alias' with a description. The tool description enhances this by giving examples of valid labels and explaining the purpose behind the parameter ('Label what this session is working on'), adding meaning beyond the raw schema.

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 immediately states the tool's function with a specific verb and resource: 'Set a custom display name for THIS agent session.' It clearly differentiates from sibling tools by specifying this is for renaming the current session in the user's Zeph app, not any other action like notifications or prompts.

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 a concrete use case: labeling sessions so the user can distinguish parallel sessions on their phone, with examples ('Prod deploy', 'Auth refactor'). It doesn't explicitly state when not to use it, but since this is a unique action among siblings, the context is clear enough.

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