Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_member_merge

DestructiveIdempotent

Merges a source member into a destination member, moving data and removing the source; omitting confirm runs a dry-run preview of the irreversible write.

Instructions

Merge one member into another. POST .../member/{member}/merge-into. Irreversible. Omit confirm for a dry-run.

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": {
      "member_id": "<member_id>",
      "destination_member_id": "<destination_member_id>"
    },
    "name": "solidtime_member_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
member_idYesSource member UUID that will be merged away.
organization_idNoOrganization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.
destination_member_idYesDestination member UUID that keeps the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description's 'Irreversible' largely restates that. The dry-run gating it mentions is also fully spelled out in the confirm parameter's schema text, so the description adds only modest context beyond the structured fields — notably nothing about what happens to the source member's data or what permissions are required.

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?

Three short, front-loaded fragments with zero filler: action, endpoint, risk, and dry-run mode. The raw URL path is arguably noise for an agent, but the telegraphic style is efficient and the irreversibility warning is correctly placed near the front.

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?

For a destructive, idempotent merge with no output schema, the definition covers the essentials an agent needs to invoke it safely, especially the dry-run/confirm gating. It could say more about what data is transferred and the fate of the merged-away member, but annotations and the scheme carry most of that remainder.

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 each of the four parameters (including the confirm const, the source/destination member UUIDs, and the organization fallback) is documented in the schema. The description mirrors the dry-run idea but adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb and resource ('Merge one member into another') and names the exact endpoint, which is unambiguous and clearly distinct from sibling operations like solidtime_member_update and solidtime_member_remove. It doesn't explicitly say it is not those siblings, but the merge semantics are self-evident.

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?

'Irreversible. Omit confirm for a dry-run' gives concrete operational guidance and a recommended safe workflow (preview first). It stops short of telling the agent when to prefer merge over update/remove alternatives, so it is strong context but not full when/when-not guidance.

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