Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_dynamic_social_card_composite

Generates a complete social-card set (Open Graph, Twitter, square, story) as SVG from a title, adding a QR code, meta tags and alt text so shared links render correctly.

Instructions

[Dynamic Media] Generate a full social-card set (Open Graph, Twitter, square, story) as SVG with a QR code, meta tags and alt text Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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": "caelara_media_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 observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does supply real context: the output is SVG, the result includes QR code, meta tags and alt text, the work happens at a remote endpoint ("Calls https://media.caelaralabs.com"), and latency is quantified (p50 12 ms, p95 42 ms). It does not say whether the call is purely computational/read-only, whether auth is required, or how the four variants are returned (single payload vs four separate documents), which are the gaps an unannotated tool most needs covered.

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?

Compact and front-loaded: the capability is stated first, then supporting details. Minor blemishes — a missing sentence break between "alt text" and "Measured", and the benchmark sentence reads as appended metadata — but no sentence is redundant.

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?

For an 8-parameter generation tool with no annotations and no output schema, the description covers what is produced and roughly how fast, which is the core need. It still leaves the return contract ambiguous (multiple SVG documents vs one bundle, where meta tags and alt text surface), which matters because no output schema defines them.

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 every parameter is already documented in structured form and the baseline is 3. The description adds no parameter-level meaning — it does not mention required `title`, the theme semantics, or how `url` triggers QR/domain label behavior beyond what the schema already says.

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?

States a concrete verb ("Generate") and a specific artifact ("full social-card set") and enumerates the variants produced — Open Graph, Twitter, square, story — plus the contents (SVG, QR code, meta tags, alt text). That level of enumeration lets an agent distinguish it from single-purpose siblings like caelara_media_edge_og_svg_generator or caelara_media_qr_code_svg_builder without opening a schema.

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 phrase "full social-card set" signals it is the choice when several card formats are needed at once, versus a narrower sibling. There is no explicit when-to-use statement, no exclusion of alternatives (e.g. when to prefer the OG-only generator), and no stated prerequisites.

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

Deploy Server

Other Tools