Skip to main content
Glama

fc_get_space

Retrieve detailed information about a specific community space using its unique ID to access space configurations, settings, and content details.

Instructions

Get detailed information about a specific space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe ID of the space to retrieve

Implementation Reference

  • Handler function for fc_get_space tool. Makes a GET request to the WordPress REST API endpoint for the specific space and returns the JSON response.
    fc_get_space: async (args: any) => {
      try {
        const response = await makeWordPressRequest('GET', `fc-manager/v1/spaces/${args.space_id}`);
        return { toolResult: { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] } };
      } catch (error: any) {
        return { toolResult: { isError: true, content: [{ type: 'text', text: `Error: ${error.message}` }] } };
      }
    },
  • Zod input schema for fc_get_space tool, requiring space_id as a number.
    const getSpaceSchema = z.object({
      space_id: z.number().describe('The ID of the space to retrieve')
    });
  • Tool registration entry in fluentCommunityTools array, defining name, description, and input schema.
    {
      name: 'fc_get_space',
      description: 'Get detailed information about a specific FluentCommunity space',
      inputSchema: { type: 'object', properties: getSpaceSchema.shape }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), implying it's likely non-destructive, but doesn't specify authentication needs, rate limits, error conditions, or what 'detailed information' entails in the response. This leaves significant gaps for a tool that retrieves data.

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 front-loads the core purpose ('Get detailed information about a specific space') with zero wasted words. It's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a data retrieval tool. It doesn't explain what 'detailed information' includes in the return values, potential response formats, or error handling. For a tool with no structured output documentation, this leaves the agent guessing about behavioral outcomes.

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 'space_id' parameter clearly documented. The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('detailed information about a specific space'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'fc_get_space_analytics' or 'fc_get_post', which also retrieve 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. It doesn't mention when to choose this over 'fc_list_spaces' for listing multiple spaces or 'fc_get_space_analytics' for analytics data, nor does it specify any prerequisites or exclusions for usage.

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/wplaunchify/fluent-community-mcp'

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