huly_list_teamspacesList all teamspaces to get the teamspaceId required before creating documents. Use this to identify available spaces for document creation.
List all teamspaces (the spaces documents live in). You need a teamspaceId from here before creating a document.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'List all teamspaces' unambiguously signals a read-only operation with no side effects, and the parenthetical adds semantic context about what a teamspace is. Though it doesn't describe response format or pagination, the operation is simple enough that the description is adequately transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core action is stated first, followed by a brief clarifying explanation and the use case. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of a parameterless list tool with no annotations or output schema, the description covers everything an agent needs: what it does, what a teamspace is, and why the result matters (obtaining a teamspaceId). Nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is no parameter semantics to document. The description correctly avoids inventing constraints and stays focused on the operation itself. This is the appropriate baseline for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' with the resource 'teamspaces' and clarifies their role ('the spaces documents live in'), which immediately distinguishes them from sibling list tools like huly_list_projects and huly_list_documents. An agent can understand exactly what this tool returns without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states the primary use case: 'You need a teamspaceId from here before creating a document,' giving clear context for when to call this tool. It does not explicitly name alternatives or exclusions, but the purpose is specific enough that an agent can infer when this is the right choice among sibling list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.