Skip to main content
Glama

Inspect a workspace

get_workspace
Read-onlyIdempotent

Returns an accessible workspace’s members, projects, invitations and pending project transfers. Current membership is required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesExact workspace ID from list_workspaces. Never infer a workspace from a project name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds genuinely new context beyond them: an authorization precondition (current membership required) and the fact that this is an aggregate read spanning four related collections rather than a single record.

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, zero filler: the returned payload is front-loaded and the access precondition follows. Nothing restates the title or name.

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?

With no output schema, the description correctly compensates by enumerating the four returned collections, and it states the membership precondition. The only remaining gap is whether the response is paginated or truncated for large workspaces, which an agent calling this correctly would not strictly need.

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?

Only one parameter exists and schema coverage is 100%, with the schema already warning to take the exact ID from list_workspaces and never infer it from a project name. The description adds no syntax or format detail beyond reinforcing the access requirement, so the baseline of 3 is appropriate.

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 names a specific verb ('Returns') and resource ('a workspace') and enumerates the payload: members, projects, invitations, and pending project transfers. That enumeration distinguishes it from list_workspaces (which enumerates workspaces rather than their contents), though it does not explicitly contrast with get_project for project-level detail.

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 context is implied rather than stated: 'accessible workspace' plus 'Current membership is required' tells the agent the calling precondition, and the schema points to list_workspaces as the ID source. There is no explicit when-to-use/when-not-to-use guidance or named alternative for retrieving project-level data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources