bettermode_get_networkGet top-level info about the Bettermode community ("network") this token belongs to — id, name, primary domain/subdomain, status, creation date, and total member count. No arguments. Bettermode GraphQL query: network.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true; description adds return field details and the GraphQL query source, but no additional behavioral traits beyond what annotations cover.
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, front-loaded with purpose, no superfluous details. Every sentence earns its place.
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 read-only tool with no output schema, the description adequately lists returned fields and purpose. Could be enhanced with authentication context, but not necessary.
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?
No parameters; schema coverage is 100%; description explicitly states 'No arguments', which is helpful and meets the baseline for zero-parameter tools.
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?
Clearly states it retrieves top-level community info, listing specific fields (id, name, domain, etc.), and distinguishes from sibling tools that target specific entities or lists.
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?
Implies usage for network-level queries; no explicit when-not or alternatives, but the context is clear and the tool is simple.
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.