Create a new AI entity on Subfeed.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Entity name | |
| topP | No | ||
| model | No | Model ID from subfeed_list_models | |
| maxTokens | No | ||
| description | No | Public description | |
| temperature | No | ||
| systemPrompt | No | System prompt |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. The one-line description only states that it creates an entity, but fails to mention side effects, idempotency, required permissions, error behaviors, or any other operational traits. This is a significant transparency gap for a mutating operation.
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 a single, front-loaded sentence with zero waste. It immediately states the tool's purpose and is appropriately concise for such a simple action, even though more content might be desirable for completeness.
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?
Despite having 7 parameters and no output schema, the description provides no information about what fields are expected, what an AI entity is, what the response will look like, or how this tool fits into the broader Subfeed workflow. The schema fills some gaps, but overall the description is insufficient for an agent to fully understand the tool's context.
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 description does not mention any parameters or their roles, and the schema covers only 57% of parameters (name, model, description, systemPrompt have descriptions, while topP, maxTokens, and temperature do not). The description adds no value beyond the schema, and a moderate coverage gap remains unaddressed.
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) and the resource (AI entity) on Subfeed, effectively distinguishing it from sibling tools like update, delete, or list. However, it does not provide additional context about what an 'AI entity' specifically entails, leaving some ambiguity about the tool's exact scope.
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 given about when to use this tool versus alternatives such as subfeed_update_entity or subfeed_publish_entity. There are no prerequisites, caveats, or context indicating the appropriate scenarios for creation.
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 clear, distinct operation: entity CRUD, addon management, discovery, interaction, and registration. While chat, invoke, and webhook all involve communication, their descriptions clearly differentiate entity chat from public invocation and webhook payloads.
All tools share the 'subfeed_' prefix and use snake_case, with most following a verb_noun pattern (create_entity, delete_entity, list_addons). A few use bare verbs (chat, invoke, register) or noun-only (webhook), but the pattern is still recognizable and predictable.
15 tools is at the upper edge of the ideal range, but it matches the server's broad scope covering entities, addons, models, discovery, and user registration. Each tool serves a distinct purpose and none feel redundant.
The surface covers full entity lifecycle (create, get, update, delete, publish), addon management (enable, disable, list), entity discovery, and user registration. Minor gaps like an explicit unpublish or webhook management can be worked around via update_entity or standalone webhook sending.