Declare intended use of a piece, get licensing terms + audit-log entry. caller_id is REQUIRED (whitespace-only rejected — storyboard-pinned).
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| caller_id | Yes | ||
| intended_use | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses two behavioral traits beyond the schema: the creation of an audit-log entry and the strict validation that caller_id must not be whitespace-only. Given that no annotations are provided, this adds some context, but it lacks other useful information like permissions, reversibility, or potential side effects beyond the audit log.
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 extremely concise: two sentences, front-loaded with the core purpose, no redundant phrasing. It even packs in a behavioral constraint without unnecessary 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 tool with three required parameters and no output schema or annotations, the description covers the basic action and one side effect but misses parameter explanations and return value structure. It is minimally viable but has clear gaps, making it a 'minimum viable' score.
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 description coverage is 0%, so the description must compensate. It only explains caller_id (required, whitespace rejected), but leaves slug and intended_use completely unexplained. This is insufficient for three required parameters, especially without any schema descriptions.
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 identifies the tool's purpose: to declare intended use for a piece and receive licensing terms plus an audit-log entry. It uses specific verbs and resources, and while it doesn't name alternatives, the purpose is distinct enough from siblings like 'request_access'.
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?
No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when another tool should be used instead. The only usage hint is the caller_id requirement, which is about parameter usage, not tool selection.
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.
Most tools have clearly distinct purposes with detailed descriptions, but a few boundaries are fuzzy: leave_message vs ask_human vs leave_comment, and list_content vs list_collection could confuse an agent at first glance. Overall, the descriptions are thorough enough to disambiguate.
The naming convention is predominantly snake_case with verb_noun structure (list_content, read_blob, upsert_skill). Minor deviations exist such as the mysloodsiewnia_* prefix and British spelling in synthesise_persona_patterns, but the pattern is highly recognizable and readable.
At 41 tools, the surface area is very large for a single MCP server and exceeds the 'heavy' threshold. While each tool serves a distinct purpose, the sheer number makes the server feel bloated and harder to navigate; many tools could be grouped or pruned without losing core functionality.
The server covers a broad domain: content read/list, personas, skills management, vault CRUD (except update/delete intentionally), provenance, licensing, memory, and async question/narada workflows. Minor gaps exist like no tool to cancel a narada job or update a memory, but these are workable and the core workflows are well supported.