Skip to main content
Glama

Read one Space

spaces_get_space
Read-only

Return one Space with its notes in order, its documents (each with the url that opens it in its builder), and its members with their roles. Private lists the documents the user keeps outside every Space. A cohort Space also lists its people: the cohort's members, by name.

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": {
      "spaceId": "<spaceId>"
    },
    "name": "spaces_get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceIdYesThe Space id, from spaces_list_spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context the annotations cannot: that notes come back in order, documents carry the URL that opens them in their builder, and that Private and cohort Spaces return additional or different content. It does not mention failure behavior for an unknown or inaccessible spaceId.

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

Conciseness4/5

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

Three sentences, front-loaded with the primary return value and then the two special cases, with no filler. The third sentence's subject ("Private") is slightly ambiguous because the named entity is only implied rather than stated as "the Private Space".

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 single-parameter, read-only tool with no output schema, the description carries the return-shape burden well by describing notes, documents, and members plus the Private and cohort variations. Minor gaps remain around error conditions and whether members are always present, but nothing an agent needs in order to select and call the tool is missing.

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?

Schema coverage is 100% and the single spaceId parameter is fully documented in the schema, including format and pattern, so the baseline is 3. The description adds only indirect meaning by mentioning "Private" as a special space, which hints that certain well-known Spaces behave differently, but it never explains how to address them by id.

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 opens with a specific verb and resource ("Return one Space") and enumerates what the response contains: ordered notes, documents with builder URLs, and members with roles. An agent can tell this is the single-item read counterpart to spaces_list_spaces, though the description never names that sibling explicitly.

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?

There is no statement of when to use this tool versus spaces_list_spaces or the per-document tools like tools_get_document. The only routing hint lives in the schema ("from spaces_list_spaces"), not the description, so usage must be inferred from the tool name.

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