Skip to main content
Glama
Sign In
cotti-admin-mcp

cotti-admin-mcp

by zchangechen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

activity_edit_save

Save edits to an existing activity, updating its time, landing page, and title, without creating a duplicate.

Instructions

Edit existing activity (修改): time, landing page, title. Not copy.

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": {
      "country": "<country>",
      "activityId": "<activityId>",
      "activityNo": "<activityNo>"
    },
    "name": "activity_edit_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry code (ID, MY, VN, HK, MO, SG, AU)
activityIdYes
activityNoYes
activityDateNoYYYYMMDD optional
landPageTitleNo
landingImagePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description does not disclose permissions, side effects, or behavior beyond 'edit'. Insufficient for a mutation tool.

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?

Very concise single sentence with key information, though the Chinese parenthetical is slightly repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Incomplete for 6-parameter tool with no output schema or annotations; missing details on return value, prerequisites, and full parameter semantics.

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?

Description maps 'time, landing page, title' to schema properties (activityDate, landPageTitle, landingImagePath), but other parameters (activityId, activityNo, country) remain unexplained. Schema coverage is 33%.

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?

Explicitly states 'Edit existing activity' with editable fields (time, landing page, title). Distinguishes from sibling 'activity_copy_save' via 'Not copy'.

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?

Indicates usage for editing (not copying), but lacks broader guidance on when to use this tool versus other siblings like activity_get or activity_set_online.

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