Skip to main content
Glama
Sign In
teamhood-mcp

teamhood-mcp

Official
by digiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Workspaces opvragen

teamhood_list_workspaces

List all workspaces in Teamhood with their IDs, providing the workspace ID needed as a starting point for almost every other query.

Instructions

Geeft alle workspaces in het Teamhood-account, met hun ID. Begin hier: bijna elke andere query heeft een workspace-ID nodig.

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": "teamhood_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns all workspaces with their IDs, which is useful. However, it doesn't mention whether this is a read-only operation, pagination behavior, or any rate limits. The description is adequate but not rich.

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?

Two sentences, front-loaded with the core purpose and the key usage hint. No wasted words.

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 zero-parameter list tool, the description is complete enough. It tells the agent what it returns and why it matters. It could mention the output format, but with no output schema and no params, the description covers the essential context.

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?

The tool has 0 parameters, so the schema is trivially complete. The description adds context about what the response contains (workspace IDs), which is helpful. Baseline for 0 params is 4, and the description earns it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all workspaces in the Teamhood account and includes their IDs. It also distinguishes itself from siblings by noting it's the starting point for most other queries that need a workspace ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Begin hier' (start here) and explains that almost every other query needs a workspace ID, which tells the agent when to use this tool before others. This is strong usage guidance.

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