bettermode_get_spaceGet a single space by its id OR its slug (provide exactly one). Returns the space's name, slug, description, type, creation date, and member/post counts. Bettermode GraphQL query: space.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | The space's id. Provide this OR `slug`. | |
| slug | No | The space's URL slug. Provide this OR `id`. |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the exactly-one-key constraint and enumerates the returned fields, but says nothing about error behavior for a missing/invalid id or slug, or whether the result can be empty.
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 the identifier constraint and followed by the return summary; no filler or restated title.
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?
There is no output schema, so the enumeration of returned fields (name, slug, description, type, creation date, member/post counts) usefully fills that gap, and the input contract is fully specified. Nothing an agent needs to call this correctly is missing.
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% and both properties already document the 'Provide this OR id/slug' rule, so the baseline would be 3. The description adds the mutual-exclusivity enforcement ('exactly one'), which sharpens the schema's softer 'OR' wording and prevents an agent from passing both.
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?
States a specific verb and resource ('Get a single space') and names the two lookup keys, which cleanly separates it from the sibling list_spaces. It even maps to the underlying Bettermode GraphQL query, so an agent can place it precisely.
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 gives an operational constraint ('provide exactly one' of id or slug), which implies the lookup scenario, but never states when to prefer this over list_spaces or search. Usage is inferable rather than stated.
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.