Skip to main content
Glama
Sign In

findtime.io MCP Server

by io.github.hkchao
OverviewDiscussionsAdmin

Rename a saved group

rename_team
Destructive

Renames a homepage Saved group. teamId is the current exact name. nextName is the new name. Cities stay on the group. The new name must not already exist. Without an account, returns teams_not_persisted.

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": {
      "teamId": "<teamId>",
      "nextName": "<nextName>"
    },
    "name": "rename_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesCurrent exact group name.
nextNameYesNew exact group name.
_endUserIdNoOptional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-idempotent; the description adds valuable context beyond that, including that cities remain on the group, that the new name must be unique, and that an unauthenticated call returns teams_not_persisted. It does not state whether the rename is reversible or what a successful response contains.

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?

Four short sentences, each adding a distinct fact: operation, parameter meanings, side effect, uniqueness constraint, and auth error. The most important information is front-loaded with no wasted text.

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?

The description covers the operation, key semantics, side effects, uniqueness requirement, and an auth failure mode. With annotations carrying the safety profile and no output schema to explain, the remaining gap is minor missing detail such as behavior when the group does not exist.

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?

Schema coverage is 100%, so the baseline is 3. The description earns an extra point by clarifying that teamId is the current exact name (important because the parameter name misleadingly suggests an ID) and by stating the uniqueness constraint on nextName.

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?

The description opens with a specific verb+resource: 'Renames a homepage Saved group,' and clarifies that teamId is the current name while nextName is the replacement. It is clearly distinct from siblings like save_team or delete_team, though it does not explicitly name an alternative.

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?

Usage is implied by the rename context and by constraints such as 'The new name must not already exist' and the unauthenticated error case. However, there is no explicit guidance about when to use this versus save_team, delete_team, or get_team.

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

All findtime.io MCP Server 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