reload_personas
Reload all AI personas from the directory to apply updates or additions to the persona list.
Instructions
Reload all personas from the personas directory
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Reload all AI personas from the directory to apply updates or additions to the persona list.
Reload all personas from the personas directory
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose side effects (e.g., does it replace current personas? Does it affect active persona?) or safety implications. It only states the action without behavioral context.
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?
Extremely concise single sentence. No wasted words. Front-loaded with action and resource.
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?
With no output schema, no annotations, and zero parameters, the description is insufficient. It lacks information about return values, side effects, or any pre/post conditions.
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, so schema coverage is complete. The description adds scope ('all personas') but no further param detail needed. Baseline 4 applies with zero parameters.
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 verb 'Reload' and the resource 'all personas from the personas directory'. This distinguishes it from sibling tools that activate, deactivate, get, or list personas.
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 on when to use this tool versus alternatives or prerequisites. The description does not indicate that this is for refreshing from disk after changes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vaibhavkkk/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server