Skip to main content
Glama
nulab

Backlog MCP Server

get_space

Retrieve details about your Backlog workspace, including project settings and configuration, to manage team collaboration and track development progress.

Instructions

Returns information about the Backlog space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler that implements the 'get_space' tool logic by calling the Backlog client's getSpace method.
    handler: async () => backlog.getSpace(),
  • Defines the empty input schema for the get_space tool.
    const getSpaceSchema = buildToolSchema((_t) => ({}));
  • Specifies the input schema (empty), output schema (SpaceSchema), and important fields for the get_space tool.
    schema: z.object(getSpaceSchema(t)),
    outputSchema: SpaceSchema,
    importantFields: ['spaceKey', 'name', 'lang', 'timezone'],
  • Instantiates and registers the get_space tool within the 'space' toolset group.
    getSpaceTool(backlog, helper),
  • Imports the getSpaceTool factory function.
    import { getSpaceTool } from './getSpace.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a read operation ('Returns information'), which implies non-destructive behavior, but lacks details on permissions, rate limits, response format, or error handling. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose and appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'information about the Backlog space' includes (e.g., metadata, settings, or structure), which could be important for an agent to understand the return value without an output schema.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but that's appropriate given the schema completeness. A baseline of 4 is assigned since no parameters exist and the schema fully covers them.

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 clearly states the verb ('Returns') and resource ('information about the Backlog space'), making the purpose understandable. However, it doesn't distinguish this tool from other 'get_' siblings like get_project or get_issue, which also return information about specific resources, so it misses full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like get_project or get_issues that retrieve specific resources, there's no indication of what makes 'space' information unique or when it's preferred over other information-retrieval tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nulab/backlog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server