solidtime-mcp

solidtime_user_email

Resends verification emails or resets pending email changes for Solidtime users; write actions require explicit confirmation.

Instructions

Pending email helpers. action resend_verification or reset_pending. Writes need confirm.

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": {
      "action": "<action>",
      "user_id": "<user_id>"
    },
    "name": "solidtime_user_email"
  }
}

Input Schema

Name	Required	Description
`action`	Yes
`confirm`	No	Set to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
`user_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the interesting unstated behavior is that this presumably triggers an outbound email; the description never mentions that external side effect or any prerequisites. "Writes need confirm" merely restates what the confirm parameter schema already documents in detail.

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, front-loaded and free of padding, but the telegraphic style leaves the sentence "Pending email helpers" doing almost no work and the structure reads like notes rather than a usable definition.

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

Completeness3/5

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

For a three-parameter mutation with no output schema, the definition omits what actually changes, whether an email is dispatched, and any permission or state preconditions. The annotations carry the safety profile and the schema carries confirm semantics, but the description does not fill the remaining gaps.

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

Parameters2/5

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

Schema description coverage is only 33%: the confirm parameter is well documented in-schema, while action and user_id are bare. The description just repeats the action enum values already visible in the schema and never explains which user user_id refers to or what the value means for the operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Pending email helpers" gestures at a domain (user email lifecycle) and the two action values hint at the operations, but no specific verb+resource is stated and the description never says it sends a verification email or resets a pending email address. An agent can guess the purpose but cannot confidently distinguish it from sibling user tools like solidtime_user_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to pick resend_verification versus reset_pending, nor when to use this tool at all versus solidtime_user_update or solidtime_members_list. The only usage-adjacent statement is "Writes need confirm," which is a mechanics note rather than a when-to-use rule.

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

Deploy Server