Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_import

Import data into a Solidtime organization using a specified importer type; omit confirmation to preview a dry run before executing the write.

Instructions

Import data into the organization. POST .../import. 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": {
      "type": "<type>",
      "data": "<data>"
    },
    "name": "solidtime_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesImport payload. Keep under 1MB in this connector.
typeYesImporter type from solidtime_importers.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
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 readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety baseline is set. The description adds genuinely non-obvious behavior: the write is opt-in and the default is a dry-run preview when confirm is omitted — an important safety trait not encoded in the annotations. It stops short of saying whether imports are atomic, reversible, or what a partial-failure looks like.

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 fragments with the core action front-loaded and the safety-critical dry-run rule at the end. The "POST .../import" fragment is mildly redundant with the tool name but cheaply conveys the HTTP operation.

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 mutating import tool there is no output schema, so the description should clarify what a dry-run returns versus a real run, and whether the payload size/blocks are validated up front. It covers the critical dry-run/commit distinction and the 1MB limit is handled by the schema, but return behavior is left entirely implicit.

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%, so all four parameters (data, type, confirm, organization_id) are already documented in detail, including the const-true constraint on confirm. The description's "Omit confirm for a dry-run" restates the schema's confirm semantics rather than adding new meaning, so this lands at the baseline.

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 ("Import data into the organization") and even names the endpoint (POST .../import), so the operation is unambiguous. It does not differentiate from nearby siblings such as solidtime_importers, solidtime_export_organization, or solidtime_organization_create, so an agent must infer that this is the write step after listing importer types.

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?

Implies usage through the dry-run instruction ("Omit confirm for a dry-run"), which tells the agent how to preview safely before committing. However, it never says when to prefer this over other organization-mutating siblings, nor that the importer type should come from solidtime_importers first — that link is only visible in the schema.

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