Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_export_organization

Exports organization data from Solidtime, with a dry-run preview by default and execution only when confirm is set to true.

Instructions

Export organization data. POST .../export. Omit confirm for a dry-run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solidtime_export_organization"
  }
}

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.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety is partly covered; the description usefully adds that omission of confirm yields a dry-run, which is behavior beyond the annotations. It does not disclose the export's scope, format, size, or whether it triggers background work or notifications, which matters for a POST-based bulk operation.

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 compact fragments, front-loaded with the action and followed by the transport and the dry-run rule; nothing is padded. The truncated 'POST .../export' path fragment is slightly cryptic, but it conveys the method efficiently.

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?

Given only two parameters, full schema coverage, and no output schema, the key gaps are disclosure of what 'organization data' includes and in what form; the dry-run hint mitigates risk substantially. For an exporter of this shape it is nearly complete, with only payload/format details missing.

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% and both parameters are thoroughly documented in-schema, including the const:true constraint and the organization_id fallback chain. The description's 'omit confirm for a dry-run' merely restates that schema text rather than adding new semantics, so the baseline of 3 applies.

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 ('Export organization data') plus the HTTP method and route, which is enough to separate it from sibling exporters like solidtime_time_entries_export. It never names those siblings explicitly, so an agent must infer the distinction by resource scope alone.

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 one sentence about omitting 'confirm' gives concrete invocation mechanics for a safe preview, which implies 'use dry-run first'. It stops short of saying when to choose this over the other export tools or what prerequisites (org membership, permissions) apply.

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