solidtime-mcp

solidtime_api_tokens

DestructiveIdempotent

List, create, revoke, or delete the current user's Solidtime API tokens, with write confirmation and redacted new token values.

Instructions

API tokens of the current user. action list, create, revoke, delete. Newly created access_token values are redacted. 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>"
    },
    "name": "solidtime_api_tokens"
  }
}

Input Schema

Name	Required	Description
`name`	No	Token name. Required for create.
`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.
`api_token_id`	No	Token UUID. Required for revoke and delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true), the description discloses two operationally important traits: newly created access_token values are redacted, and writes require confirm. That tells the agent the secret is not retrievable and that mutations are gated, which is real value the annotations do not convey.

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 sentences, front-loaded with the resource then the actions then the two key caveats; nothing is padded. The action list is delivered as a verb fragment rather than a sentence, which reads slightly clipped but wastes no words.

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?

With no output schema, the description should hint at what list returns and how revoke differs from delete; it only covers the create-side redaction. It is adequate to call the tool correctly but leaves the agent guessing about result shapes and the revoke/delete distinction.

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?

At 75% schema coverage the description must partially compensate, and 'Writes need confirm' reinforces the dry-run semantics of the confirm parameter in a way that clarifies which actions it applies to. Name and api_token_id are already documented in the schema, so no further gain is expected there.

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 names the resource precisely ('API tokens of the current user') and enumerates the four supported actions (list, create, revoke, delete). No sibling tool covers tokens, so differentiation is inherent, though the opening fragment is terse rather than a declarative sentence.

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?

It flags that writes require confirmation, which tells the agent a prerequisite for create/revoke/delete, but it offers no guidance on choosing revoke versus delete or when a token operation is appropriate. Usage is implied rather than instructed.

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

Deploy Server