solidtime-mcp

solidtime_reports

DestructiveIdempotent

List, retrieve, create, update, and delete saved reports; manage public sharing and preview write actions before confirmation.

Instructions

Saved reports. action list, get, create, update, delete. Public share uses is_public. 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_reports"
  }
}

Input Schema

Name	Required	Description
`name`	No
`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.
`is_public`	No
`report_id`	No
`description`	No
`public_until`	No
`properties_end`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`organization_id`	No	Organization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.
`properties_group`	No
`properties_start`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`properties_active`	No
`properties_tag_ids`	No
`properties_billable`	No
`properties_task_ids`	No
`properties_timezone`	No
`properties_sub_group`	No
`properties_client_ids`	No
`properties_member_ids`	No
`properties_week_start`	No
`properties_project_ids`	No
`properties_history_group`	No
`properties_rounding_type`	No
`properties_tag_match_type`	No
`properties_rounding_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructive true, openWorld true, idempotent true, and readOnly false; the description adds the useful constraint that writes require confirm. It does not explain what delete/update affect, permission needs, or return behavior beyond that.

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?

The description is four terse fragments with no filler and front-loads the resource before the action list. Its brevity contributes to completeness gaps, but as a conciseness/structure score it is efficient.

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

Completeness2/5

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

For a 25-parameter tool with destructive writes and public-sharing behavior and no output schema, the description is far too sparse. Annotations cover the safety profile, but action-specific parameter usage and the many filter fields remain unexplained.

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 16% across 25 parameters, and the description only clarifies action, is_public, and confirm. It leaves report_id, name, description, and the large properties_* filter family undocumented, so it fails to compensate for the low schema coverage.

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?

Opens with 'Saved reports' and enumerates the five actions, so the resource and supported operations are clear. It does not distinguish this tool from sibling solidtime_public_report or clarify whether saved reports include shared/public ones, so it stops short of full sibling differentiation.

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?

Only usage-like statements are 'Public share uses is_public' and 'Writes need confirm'; there is no explicit when-to-use guidance for list/get/create/update/delete or when to prefer solidtime_public_report. The agent must infer routing and prerequisites from the action enum and schema.

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

Deploy Server