Skip to main content
Glama

bettermode

by io.usefulapi

List members

bettermode_list_members
Read-only

List members of the community, with pagination. Optionally filter by a search term (query, matches name/username/email), by role (roleIds), order (orderBy), and reverse. Returns edges[].node (with role) plus pageInfo and totalCount. Bettermode GraphQL query: members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of members to return (1..100, default 10).
queryNoFilter to members matching this search term (name/username/email).
offsetNoNumber of members to skip (offset-based pagination).
orderByNoOrder field (e.g. "createdAt", "name").
reverseNoReverse the sort order.
roleIdsNoFilter to members holding any of these role ids.

TDQS

A4.5/5.0
Behavior4/5

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

Adds return structure (edges, node, role, pageInfo, totalCount) and notes it's a GraphQL query beyond readOnlyHint annotation.

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?

Two sentences, front-loaded purpose, each sentence adds value, no waste.

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

Completeness5/5

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

Explains pagination, all filters, and return structure; no output schema needed given full description.

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?

Adds meaning beyond schema by detailing what query matches and role filter; baseline 3 due to 100% schema coverage, but extra context justifies 4.

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?

Clearly states it lists community members with pagination, distinguishing it from get_member (single) and search (general).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes optional filters but does not explicitly exclude alternatives for single-member lookups or search; still clear context.

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

All bettermode toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: get vs list for members, posts, spaces, plus get_network and search. There is no ambiguity between tools.

Naming Consistency5/5

All tools follow a uniform 'bettermode_verb_noun' pattern with lowercase snake_case. Verbs are consistently 'get', 'list', or 'search'.

Tool Count5/5

With 8 tools, the server covers the essential read operations for a community platform without being overwhelming or too sparse.

Completeness2/5

The tool set is entirely read-only; there are no create, update, or delete operations for members, posts, or spaces, which are significant gaps for comprehensive community management.

Resources