Skip to main content
Glama
Im-Hal-9K

Capacities-MCP-Plus

capacities_get_space_info

Read-only

Retrieve detailed information about a specific Capacities space, including its structures and collections, by providing the space's UUID identifier.

Instructions

Get detailed information about a specific Capacities space including structures and collections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceIdYesThe UUID of the space to get information for

Implementation Reference

  • The async execute function that handles the tool logic: makes an API request to `/space-info?spaceid=${spaceId}`, parses JSON, and returns formatted string or throws error.
    execute: async (args: { spaceId: string }) => {
    	try {
    		const response = await makeApiRequest(
    			`/space-info?spaceid=${args.spaceId}`,
    		);
    		const data = await response.json();
    		return JSON.stringify(data, null, 2);
    	} catch (error) {
    		throw new Error(
    			`Failed to get space info: ${error instanceof Error ? error.message : String(error)}`,
    		);
    	}
  • Zod schema defining the input parameter 'spaceId' as a UUID string.
    parameters: z.object({
    	spaceId: z
    		.string()
    		.uuid()
    		.describe("The UUID of the space to get information for"),
    }),
  • src/server.ts:27-27 (registration)
    Registers the getSpaceInfoTool with the MCP server.
    server.addTool(getSpaceInfoTool);
  • src/tools/index.ts:2-2 (registration)
    Re-exports the tool for convenient import in server.ts.
    export { getSpaceInfoTool } from "./getSpaceInfo.js";
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating it's a safe read operation that may return partial data. The description adds value by specifying the type of information returned ('detailed information... including structures and collections'), which goes beyond annotations. It doesn't contradict annotations, but lacks details on rate limits, auth needs, or error handling.

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, well-structured sentence that efficiently conveys the tool's purpose and scope. It's front-loaded with the main action and resource, with no redundant or unnecessary information, making it easy to parse quickly.

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?

Given the tool's low complexity (1 parameter, no output schema), the description is reasonably complete. It covers what the tool does and what information it returns. However, without an output schema, it could benefit from more detail on the return format (e.g., structure of the response), but the annotations and context mitigate this gap.

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 has 100% description coverage, with the spaceId parameter fully documented as a UUID. The description doesn't add any parameter-specific details beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get detailed information') and resource ('about a specific Capacities space'), including what information is retrieved ('including structures and collections'). It distinguishes from sibling tools like capacities_list_spaces (which lists spaces) and capacities_read_object_content (which reads content of objects).

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?

The description implies usage context by specifying 'a specific Capacities space', suggesting it's for retrieving details of a known space rather than listing or searching. However, it doesn't explicitly state when to use this tool versus alternatives like capacities_search or capacities_list_spaces, nor does it mention prerequisites or exclusions.

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