create_custom_mnemonsCreate custom-typed mnemons (any free-form entry that doesn't fit the other types). Players may not call this — GM/co-GM only.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| campaignId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate a write operation (readOnlyHint=false) and no destructive intent (destructiveHint=false). The description adds the GM/co-GM permission restriction, which is valuable, but does not disclose bulk creation via the items array or any post-creation effects. The added context is helpful but not comprehensive.
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?
The description is two concise sentences, delivering purpose and access restriction with no filler. Front-loaded with the primary action.
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?
Given the nested schema and output schema, the description provides enough for tool selection but omits practical details like bulk creation support (items maxItems) and optional fields (tags, customType, visibility). However, these are available in the schema, so the description is minimally acceptable.
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?
The top-level parameters (campaignId, items) have no descriptions in the schema (0% coverage), and the description provides no parameter-level guidance. The description does not explain the structure of items or the meaning of customType, leaving the agent to infer from nested fields.
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 states the action ('Create'), the resource ('custom-typed mnemons'), and the scope ('any free-form entry that doesn't fit the other types'), effectively distinguishing it from sibling create_*_mnemons tools.
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?
It explicitly indicates when to use this tool ('any free-form entry that doesn't fit the other types') and restricts usage to GM/co-GM, but doesn't name specific alternative tools. This provides adequate situational guidance.
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 has a clearly distinct purpose. The mnemon tools are separated by type (NPC, Location, Quest, etc.), and other domains like guild, forum, and friend management are also well-segmented. No two tools appear to do the same thing.
Most tools follow a consistent verb_noun pattern with snake_case. Some minor deviations: 'describe_mnemon_types' instead of 'list_mnemon_types', and 'invite_user_by_email' has a slightly different structure. Overall quite consistent.
With 63 tools, the server is quite heavy. While each tool serves a specific purpose for campaign management, the sheer number may be overwhelming. It is borderline but still reasonable given the broad domain coverage.
The tool set covers CRUD for most resources (campaigns, sessions, mnemon types, guilds, friends, forum). Notable gaps: no delete_campaign or delete_session, and update_campaign is limited. However, the core workflows are well-covered.