Skip to main content
Glama

Set an artifact in a brand

style_artifact
Idempotent

Sets one of the account's artifacts in a company's brand (its colours, its type and its logo, read from the company's site), or back in the plain look. It writes a new version of the same content; earlier versions are kept.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "brand": "<brand>"
    },
    "name": "style_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe artifact's id, from make_artifact or list_artifacts.
brandYesThe company's domain, like acme.com, to set the artifact in that company's brand: its colours, its type and its logo. "corridome" sets it back in the plain look.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive and open-world, but the description adds real value beyond them: it discloses that the brand data is fetched from the company's site (explaining the open-world behaviour) and that the write creates a new version while earlier versions are kept, which is the key reversibility fact an agent needs. It does not cover failure modes such as an unreachable or unknown domain.

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 tight sentences: the primary action and its two modes come first, then the versioning consequence. Every clause carries information and nothing is repeated padding.

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?

For a two-parameter mutation with full schema coverage and no output schema, the description covers what changes, where the brand data comes from, and that prior versions survive. Minor gaps remain around confirmation of success and behaviour when the domain is invalid, but nothing essential for correct invocation is missing.

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 coverage is 100% and both parameters are already fully documented, including the 'corridome' reset value. The description restates the same semantics (brand domain, colours/type/logo, plain look) without adding syntax, validation or format detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description gives a specific verb ('Sets') plus the resource ('one of the account's artifacts') and the exact effect ('in a company's brand ... or back in the plain look'). It implicitly separates itself from make_artifact by operating on an existing artifact, but never names a sibling or states that distinction explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the reader infers you call this when you want brand styling applied to an existing artifact, and the id must come from make_artifact or list_artifacts (though that is carried by the schema, not the description). There is no explicit when-not guidance, no mention of prerequisites such as account/brand access, and no named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources