Skip to main content
Glama

swop

by io.github.Travisswop
OverviewDiscussionsAdmin

Edit my SmartSite (name, bio, background)

swop_update_my_smartsite

Edit the linked account's SmartSite: display name, bio, and appearance (background color, a gradient of hex stops, a background image URL, theme/font color, font family, or header layout). Pass only what you want to change. For adding links/buttons/info bars use swop_add_link; for products use swop_create_product / swop_feature_product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioNoNew bio text
nameNoNew display name
fontColorNoPrimary font hex color
fontFamilyNoFont family name
themeColorNoAccent/theme hex color
smartsiteIdNoSpecific SmartSite id (default: primary)
headerFormatNoHeader layout style
backgroundImgNoBackground/wallpaper image URL
backgroundColorNoSolid background hex, e.g. "#0b0b0f"
backgroundGradientNoGradient hex stops, e.g. ["#5b3df5","#0b0b0f"] (clears the solid color)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / backgroundColor
      Added value: +{
+  "description": "Solid background hex, e.g. \"#0b0b0f\"",
+  "type": "string"
+}
    • addedInput schema / properties / backgroundGradient
      Added value: +{
+  "description": "Gradient hex stops, e.g. [\"#5b3df5\",\"#0b0b0f\"] (clears the solid color)",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
    • addedInput schema / properties / backgroundImg
      Added value: +{
+  "description": "Background/wallpaper image URL",
+  "format": "uri",
+  "type": "string"
+}
    • addedInput schema / properties / fontColor
      Added value: +{
+  "description": "Primary font hex color",
+  "type": "string"
+}
    • addedInput schema / properties / fontFamily
      Added value: +{
+  "description": "Font family name",
+  "type": "string"
+}
    • addedInput schema / properties / headerFormat
      Added value: +{
+  "description": "Header layout style",
+  "enum": [
+    "centered",
+    "left",
+    "cover",
+    "hero",
+    "orbit",
+    "card",
+    "bar"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / themeColor
      Added value: +{
+  "description": "Accent/theme hex color",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate it's a write operation (readOnlyHint false) but not destructive (destructiveHint false). The description adds the partial-update behavior ('pass only what you want to change') and that backgroundGradient 'clears the solid color' (though that is also in the schema). It provides useful context beyond generic annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two well-structured sentences, front-loaded with the core purpose and followed by routing guidance. No wasted words; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 optional parameters with full schema descriptions and no output schema, the description covers the overall scope and usage clearly. It could mention return behavior or error scenarios, but for a partial-update tool with clear schemas, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% parameter descriptions, so baseline is 3. The description lists the parameter categories but does not add new semantics beyond the schema's existing per-field descriptions. It repeats what the schema already says, so it adds no extra value here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool edits the linked account's SmartSite and explicitly lists the fields (name, bio, background, theme, font, header layout). It distinguishes from siblings by naming alternatives for adding links and products, so an agent knows exactly what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when NOT to use this tool: for links/buttons/info bars use swop_add_link, for products use swop_create_product / swop_feature_product. It also instructs to 'pass only what you want to change', giving clear usage intent. This is excellent routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All swop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources