swebsy_get_builder_guideLoad static Swebsy builder guidance on components, theme classes, and conventions to help coding agents follow the in-app AI Builder's rules.
Load the static Swebsy builder guidance (component system, theme classes, conventions) that the in-app AI Builder is primed with.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds that the content is 'static' and pre-primed into the AI Builder, which usefully reinforces that repeated calls return the same guidance, but it discloses nothing about return format or size beyond that.
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?
One sentence, front-loaded with the verb and resource, with a compact parenthetical enumerating the content. Every clause carries information and there is no filler.
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 parameterless, read-only reference loader with no output schema, the description tells the agent what guidance it receives (component system, theme classes, conventions), which is most of what is needed. It stops short of indicating the form of the returned content or whether the same doc is retrievable by other means.
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 tool takes zero parameters and the schema is empty with additionalProperties=false, so there is no parameter semantics for the description to clarify. Baseline of 4 applies since nothing is left ambiguous for the caller.
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 (Load) and a specific resource (static Swebsy builder guidance), and enumerates what it contains: component system, theme classes, conventions. It does not differentiate itself from the adjacent swebsy_get_skill, which likely also loads reference documentation, so the sibling boundary is left to inference.
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?
Usage is only implied: an agent infers it should call this before writing sections/pages to learn the conventions. There is no explicit statement of when to load it versus swebsy_get_skill, swebsy_list_skills, or the builder-guidance-adjacent siblings, and no exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.