Apply a stereotype to a model element by qualified name, enabling classification and domain-specific extension within SysML models.
Apply a stereotype to an element by its qualified name.
| Name | Required | Description | Default |
|---|---|---|---|
| element_id | Yes | ||
| stereotype_qn | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It only states the action without disclosing side effects, idempotency, error conditions, or whether it replaces existing stereotypes. For a mutation tool, this is insufficient.
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?
Single, front-loaded sentence with no wasted words. Efficiently communicates the core 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 simplicity, the description is minimal but lacks important context such as whether the operation is idempotent, whether it fails on invalid input, and any usage constraints. The output schema is present but its contents are unknown, and the description does not mention return behavior. Incomplete for a mutation tool with no annotations.
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 0% and the description only clarifies stereotype_qn as a qualified name. It does not explain element_id, its format, or how to obtain it. The description adds minimal meaning beyond the parameter names.
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 (apply) and resource (stereotype to an element) and identifies the stereotype by qualified name. Clearly distinguishes from remove_stereotype and other set_* 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?
No explicit guidance on when to use this tool vs alternatives. Does not mention that remove_stereotype exists for removing, or any prerequisites such as the element existing or stereotype being applicable. The agent must infer usage from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.