Skip to main content
Glama
Sign In
solidtime-mcp

solidtime-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

solidtime_user_set_organization

Idempotent

Switches the active organization for your Solidtime user account via a dry-run or confirmed write, resolving the organization from the given UUID, environment variable, or your memberships.

Instructions

Set the current organization. PUT /api/v1/users/me/current-organization. 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_user_set_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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered. The description adds a two-step confirm/dry-run safety posture, but that same fact is already spelled out in the confirm parameter's schema description, so the value over structured fields is modest. It says nothing about what changes downstream after the switch or whether the current selection persists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact fragments, front-loaded with the action and immediately followed by the endpoint and the dry-run caveat. There is no filler, and each sentence carries distinct information.

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?

For a two-parameter state-switching tool with no output schema and full schema coverage, the definition covers action, endpoint, and the confirm gate. The main remaining gap is the effect of the switch on subsequent tool calls, which matters for a context-changing operation but is a relatively small omission.

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?

Schema description coverage is 100%, including the confirm dry-run semantics and the organization_id fallback chain (env var, then memberships lookup), so the schema does the heavy lifting. The description's mention of omitting confirm for a dry-run is consistent with, though redundant to, the schema, so this lands at the high baseline rather than above it.

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 states a specific verb and resource: 'Set the current organization', with the underlying endpoint (PUT /api/v1/users/me/current-organization) confirming it is a session/context switch rather than an organization record edit. It does not explicitly contrast itself with nearby siblings such as solidtime_organization_update or solidtime_organization_get, so differentiation is left partly to the tool name.

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?

Usage is only implied: the agent can infer 'use this to change which organization subsequent calls act on', but the description never says when to call it, what prerequisite state exists, or which sibling to use instead for editing organization details. The dry-run hint gives a procedural cue but not 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

Other Tools