Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_member_remove

DestructiveIdempotent

Permanently removes a member from a Solidtime organization. Omit confirm to run a dry-run preview before executing this irreversible deletion.

Instructions

Remove a member. DELETE .../members/{member}. 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>"
    },
    "name": "solidtime_member_remove"
  }
}

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_idYes
organization_idNoOrganization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description still adds value by stating the effect is irreversible and by advertising a dry-run mode via omitted confirm, which is a behavioral trait not encoded in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments with no filler, and the destructive/irreversible warning is front-loaded. It is efficient but telegraphic, with no sentence connecting the warning to the actual consequence of the call.

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 single-resource delete with annotations and a fully typed schema, the description covers the key risks: irreversibility and a dry-run escape hatch. It omits secondary context such as required permissions or what happens to the member's time entries and memberships, which an agent might want before executing.

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 coverage is 67% and the confirm and organization_id parameters already carry their own descriptions, including the dry-run and fallback resolution rules. The description's dry-run sentence largely restates what confirm's schema text says, and member_id gets no added meaning beyond its name.

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 ('Remove a member') plus the REST path DELETE .../members/{member}, which unambiguously separates it from solidtime_member_update, solidtime_member_merge, and the placeholder/invitation tools. It stops short of naming any sibling explicitly, so a 4 rather than a 5.

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?

The 'Omit confirm for a dry-run' line gives concrete invocation guidance for the confirm parameter, and 'Irreversible' implies caution before calling. There is no guidance on when to use this versus alternatives (e.g., removing a membership vs. a user, or vs. member_merge), so usage is implied rather than stated.

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