Skip to main content
Glama
Sign In
resolve-mcp

resolve-mcp

by irstone-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

timeline_rename

Rename a timeline to a unique new name within your project, ensuring no duplicates.

Instructions

Rename a timeline. Names must be unique within the project.

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": {
      "new_name": "<new_name>"
    },
    "name": "timeline_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYes
name_or_handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided. Description only adds uniqueness constraint but does not disclose error behavior, idempotency, or effects on references. Limited transparency 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?

Two short sentences with no fluff. Could add parameter info without significant length increase, but still concise and front-loaded.

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 a 2-param tool with no output schema or annotations. Missing explanation of 'name_or_handle', which timeline is renamed, and side effects. Not sufficient for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Does not explain 'name_or_handle' parameter or which timeline is renamed. Ambiguity about whether it acts on current timeline or specified one. Description fails to clarify.

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?

Clear verb+resource: 'Rename a timeline.' Adds constraint 'Names must be unique within the project.' Distinguishes from siblings like timeline_create, timeline_duplicate, and track_rename.

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?

States basic use case but no explicit when-not-to-use or alternatives. The uniqueness constraint provides some guidance, but lacks context like whether to use timeline_info first or alternatives like timeline_duplicate.

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