Skip to main content
Glama
thenavidm

Fluent WordPress MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc space members

fc_space_members
Read-onlyIdempotent

Retrieve paginated active members of a FluentCommunity space, including profiles, roles, and pending join request counts. Filter by search, status, and sort order.

Instructions

Returns the paginated active membership of a space, each entry carrying the member profile and their role, plus the count of outstanding join requests.

Controller: SpaceController@getMembers Route source: fluent-community/app/Http/Routes/api.php:18

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSpaceSlug extracted from the URL path.
searchNoSearch read via `$request->getSafe()` in getMembers().
statusNoStatus read via `$request->get()` in getMembers().
accountNoExact configured private account profile label; not a tenant or provider account ID.
sort_byNoSort By read via `$request->getSafe()` in getMembers().created_at
sort_dirNoSort Dir read via `$request->getSafe()` in getMembers().

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read profile. The description adds that results are paginated and include outstanding join request counts, but doesn't explain pagination mechanics or any auth/permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is dense and front-loads the core behavior. However, the subsequent controller/route source lines are developer-oriented provenance metadata that doesn't help an agent decide or invoke the tool, adding length without aiding usage.

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?

For a read-only list tool with full annotation coverage and complete schema descriptions, the definition is adequate. But it lacks guidance on pagination behavior, alternative tools for member analytics, or how the join-request count should be interpreted, leaving some contextual gaps for an agent.

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?

Schema description coverage is 100%, so the schema already documents all six parameters including constraints and the special 'account' clarification. The description doesn't add parameter-level detail beyond what the schema provides, which is the baseline expectation.

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?

States a specific verb (Returns) and resource (paginated active membership of a space), plus names exactly what each entry carries. This clearly distinguishes it from siblings like fc_list_spaces or fc_analytics_member_activity.

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 through 'active membership' but doesn't state when to use this tool versus alternatives like fc_analytics_top_members or fc_list_spaces. No explicit when/when-not guidance is provided.

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