Skip to main content
Glama
Sign In
docmost-community-mcp

docmost-community-mcp

by dilruwanm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_space

Read-only

Retrieve a space's details and your membership status by supplying its UUID or slug. Confirms access levels and space information.

Instructions

Get details for a space, including the current user's membership.

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": {
      "space_id": "<space_id>"
    },
    "name": "get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYesSpace UUID or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral detail—that the result includes the current user's membership—but does not disclose failure behavior, required permissions, or what 'details' generally includes.

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?

A single, front-loaded sentence that states the main action and the notable membership detail with no filler. Every word earns its place.

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 simple read-only tool with one fully documented parameter and strong safety annotations, the description is nearly sufficient. The only notable gap is the lack of an output schema and no enumeration of which 'details' are returned, but an agent can still invoke it correctly with just the space_id.

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?

The input schema fully documents space_id as 'Space UUID or slug' with 100% coverage. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score 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 uses a specific verb ('Get') and resource ('space'), and narrows the scope to a single space plus the current user's membership. It is clear, though it does not explicitly name or contrast sibling tools such as list_spaces or list_space_members.

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

Usage Guidelines4/5

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

The context is clear: use this tool when you need details for one space, including the current user's membership. It does not explicitly mention alternatives or exclusion conditions, but the singular 'a space' implies the single-item retrieval use case.

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