Skip to main content
Glama
Im-Hal-9K

Capacities-MCP-Plus

capacities_list_spaces

Read-only

Retrieve all personal spaces in Capacities knowledge management to organize and access your information.

Instructions

Get a list of all personal spaces in Capacities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function that handles the tool logic: makes an API request to /spaces, parses JSON, and returns formatted string.
    execute: async () => {
    	try {
    		const response = await makeApiRequest("/spaces");
    		const data = await response.json();
    		return JSON.stringify(data, null, 2);
    	} catch (error) {
    		throw new Error(
    			`Failed to list spaces: ${error instanceof Error ? error.message : String(error)}`,
    		);
    	}
    },
  • Tool name and parameters schema (empty object, no input parameters required). Also includes annotations and description above.
    	name: "capacities_list_spaces",
    	parameters: z.object({}),
    };
  • src/server.ts:26-26 (registration)
    Registers the listSpacesTool with the FastMCP server.
    server.addTool(listSpacesTool);
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with potentially dynamic data. The description adds minimal behavioral context beyond this, only specifying 'all personal spaces' without detailing format, pagination, or error handling. No contradiction with annotations exists.

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 purpose without unnecessary words. It's front-loaded with the core action ('Get a list'), making it easy to parse quickly.

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's simplicity (0 parameters, read-only operation) and lack of output schema, the description is adequate but minimal. It covers the basic purpose but doesn't provide details on return format, error cases, or usage context, which could help an agent better understand how to integrate results.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the input structure (none required). The description adds no parameter-specific information, which is acceptable here as there are no parameters to explain, maintaining clarity without redundancy.

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 ('Get') and resource ('all personal spaces in Capacities'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'capacities_get_space_info' which might retrieve details about a specific space versus listing all spaces.

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. It doesn't mention sibling tools like 'capacities_search' for filtered searches or 'capacities_get_space_info' for detailed information about specific spaces, leaving the agent without context for tool selection.

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/Im-Hal-9K/Capacities-MCP-Plus'

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