bettermode_get_postGet a single post by its id. Returns title, shortContent, creation date, space, owner (member), and reaction/reply counts. Bettermode GraphQL query: post.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The post's id. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. Description adds value by enumerating returned fields, confirming the read-only nature. Does not discuss errors or auth, but given the readOnlyHint, transparency is adequate.
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?
Concise two-sentence description with front-loaded action. No unnecessary information; every sentence serves a purpose.
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 retrieval tool with no output schema, the description lists all key return fields. No missing critical context for an agent to use the tool correctly.
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 describes the single parameter 'id' fully (100% coverage). Description does not add extra meaning beyond what the schema provides, so baseline score of 3 is appropriate.
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 the tool retrieves a single post by its ID and lists the returned fields (title, shortContent, etc.). Distinguishes from sibling tools like bettermode_list_posts which return multiple posts.
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?
Implicitly indicates usage when a specific post ID is known. Does not explicitly compare to list_posts or specify when not to use, but the purpose is clear enough for an agent to decide.
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.