Skip to main content
Glama
Sign In

Nevent MCP

by io.github.nevent-dev
OverviewDiscussionsAdmin

nevent_rename_template

Destructive

Rename an email template without modifying its content (lightweight — no re-render triggered). Use after nevent_clone_template to give the clone a proper name, or to reorganize existing templates. Returns the updated template with the new name. Next step: nevent_update_template to change content, or nevent_preview_template to validate rendering.

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": {
      "template_id": "<template_id>",
      "name": "<name>"
    },
    "name": "nevent_rename_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name for the template. Must be between 1 and 255 characters. Duplicate names are allowed by the API.
template_idYesThe ID of the email template to rename. Use nevent_list_templates to get valid template IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses a meaningful behavioral trait beyond the annotations: 'no re-render triggered', which is not apparent from readOnlyHint=false or destructiveHint=true. It also states the return value ('Returns the updated template'). The destructiveHint is not elaborated, but the lightweight guarantee and return behavior add useful context.

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?

Three tight sentences with no fluff. The main purpose and key trait are front-loaded, followed by usage context and next steps. 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?

Given this is a simple 2-parameter rename operation with no output schema and annotations covering read-only/destructive hints, the description is complete: it explains what happens, when to use it, the return value, and what to do next. An agent has everything needed to call it correctly.

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 description coverage is 100%, and both parameters already have clear descriptions: name includes length rules and duplicate allowance, template_id includes a lookup hint. The description doesn't add new parameter-level detail, but the schema fully carries that weight, so baseline 3 is appropriate.

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 and resource: 'Rename an email template without modifying its content'. It distinguishes itself from update_template by emphasizing no content change and from clone_template by its rename purpose. The 'lightweight — no re-render triggered' clause makes the tool's unique role unmistakable.

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 tells when to use: 'Use after nevent_clone_template to give the clone a proper name, or to reorganize existing templates.' It also names the next steps for content changes and rendering validation. This is clear routing guidance with named alternatives.

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

All Nevent MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources