bettermode_get_memberGet a single community member by their id. Returns name, username, email, status, creation date, role, and tagline. Bettermode GraphQL query: member.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The member's id. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, so the description adds little beyond mentioning the underlying GraphQL query. No additional behavioral traits like error handling or auth needs are disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with front-loaded purpose and efficient listing of return fields. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 1-parameter tool with no output schema, the description adequately covers what the tool returns and how to use it. Could include error handling for missing members but overall sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear description for the id parameter. The description repeats the parameter usage but adds no extra meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the action ('Get a single community member'), the resource ('by their id'), and lists the return fields, distinguishing it from sibling tools like bettermode_list_members.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving a single member by ID but does not explicitly state when to use vs alternatives like bettermode_list_members or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
All tools follow a uniform 'bettermode_verb_noun' pattern with lowercase snake_case. Verbs are consistently 'get', 'list', or 'search'.
With 8 tools, the server covers the essential read operations for a community platform without being overwhelming or too sparse.
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.