Skip to main content
Glama

Caelara Labs Dynamic Media

edge_og_svg_generator

Render an Open Graph card (default 1200x630) as SVG

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": "edge_og_svg_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (hex, with or without #)
fgNoText color (hex, with or without #)
brandNoBrand label
themeNodark (default) or light
titleYesHeadline
widthNoWidth in px (200-4000, default 1200)
accentNoAccent color (hex, with or without #)
formatNojson (default, includes svg + data URI) or svg (raw image/svg+xml)
heightNoHeight in px (200-4000, default 630)
subtitleNoSupporting line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it: it says nothing about side effects, auth, or determinism, and crucially it says output is SVG while the schema's format parameter defaults to json wrapping the svg plus a data URI — a mismatch an agent could act on wrongly.

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 front-loaded sentence with no filler or redundancy. Its brevity is efficient rather than padded, though it is short to the point of omitting needed context.

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

Completeness2/5

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

With ten parameters, no annotations, and no output schema, the description should at minimum characterize the return payload (JSON with svg plus data URI vs raw image/svg+xml) and note that this is a pure generation call. None of that is covered, leaving material gaps for a fairly configurable tool.

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%, so every one of the ten parameters (bg, fg, accent, theme, brand, title, subtitle, width, height, format) is already documented inline, including defaults and bounds. The description adds only the default dimensions, which the schema also states, so 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?

Specific verb plus resource: 'Render an Open Graph card ... as SVG', with a default size stated. It is distinguishable from composite siblings like dynamic_social_card_composite or brand_kit_composite by being a direct OG-card SVG renderer, though it never names an alternative or scope boundary explicitly.

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?

No when-to-use or when-not-to-use guidance, and no routing to or away from the composite/OG siblings. The agent must infer the context from the resource name alone.

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