solidtime-mcp

solidtime_projects_list

Read-only

Lists projects visible to the current user, with optional pagination and archived filtering, so MCP clients can discover available projects before managing time entries or tasks.

Instructions

List projects visible to the current user. GET .../projects. Optional page and archived.

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_projects_list"
  }
}

Input Schema

Name	Required	Description
`page`	No
`archived`	No
`organization_id`	No	Organization 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.

First observedv0.1.0Nov 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by saying results are limited to projects visible to the current user and by noting the GET endpoint. However, it does not explain pagination behavior, default archived handling, or response shape.

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?

The description is very short and front-loaded, with no wasted sentences. The endpoint line and the optional parameter note are terse but relevant, and the core purpose appears first.

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 simple read-only list tool, the description is minimally adequate: it states scope, endpoint, and optional filters. However, with low schema coverage and no output schema, it should clarify archived filter semantics and pagination behavior. The current text leaves meaningful ambiguity for an agent invoking the tool.

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 33%, so the description needs to compensate for undocumented parameters. It names 'page' and 'archived' as optional but does not explain their semantics, especially whether 'archived' includes or excludes archived projects. It also omits organization_id, though that parameter is documented in the schema.

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 clearly states a specific verb and resource: 'List projects' scoped to those 'visible to the current user'. It also gives the endpoint, confirming this is a list operation. It does not explicitly differentiate from sibling tools such as solidtime_project_get, so it falls short of a 5.

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?

The description gives no explicit guidance on when to use this tool versus alternatives like solidtime_project_get or the create/update/delete project tools. The list operation implies its usage, but there are no exclusions or routing cues for an agent choosing among siblings.

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

Deploy Server