Skip to main content
Glama

Caelara Labs Dynamic Media

dynamic_social_card_composite

Generate a full social-card set (Open Graph, Twitter, square, story) as SVG with a QR code, meta tags and alt text

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": {
      "title": "<title>"
    },
    "name": "dynamic_social_card_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (hex, with or without #)
fgNoText color (hex, with or without #)
urlNoDestination URL; adds a QR code and domain label
brandNoBrand label shown on the card
themeNodark (default) or light
titleYesCard headline
accentNoAccent color (hex, with or without #)
subtitleNoSupporting line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the outputs produced (SVG cards in four aspect ratios, an embedded QR code, meta tags, alt text), which matters given there is no output schema. However it omits key behavior: what happens if 'url' is not supplied (is the QR code and domain label simply skipped?), whether generation is deterministic/pure, and roughly how large or how many files the result contains.

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

Conciseness4/5

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

A single sentence with zero filler, and the artifact list is front-loaded so the agent knows the scope immediately. It is dense but readable; a short clause on when to prefer a single-format sibling would be worth the extra length.

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

Completeness3/5

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

The description names the full output surface, which compensates for the absent output schema, but for an 8-parameter generator with no annotations it leaves open the conditional behavior of 'url', theme defaults, and the shape of the returned result. Adequate to invoke, not complete enough to predict the outcome.

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 description coverage is 100%, so each of the 8 parameters is already documented in the schema and the baseline of 3 applies. The description adds only indirect mapping — the mention of a QR code implies the 'url' parameter drives it — but gives no extra meaning about defaults, color fallbacks, or theme precedence.

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 opens with a specific verb ('Generate') and a specific resource ('full social-card set'), and enumerates the four variants (Open Graph, Twitter, square, story) plus the accompanying artifacts (QR code, meta tags, alt text). It does not differentiate itself from plausible siblings such as edge_og_svg_generator or qr_code_svg_builder, which is the one gap keeping it off a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement and no named alternative. The word 'full' implies 'use this when you want the complete set rather than a single format', but the agent must infer that contrast entirely; nothing tells it when to pick edge_og_svg_generator or qr_code_svg_builder instead.

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