Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_badge_shield_generator

Generate an SVG status badge with a custom label, message, and colors in flat or flat-square style for READMEs and dashboards, returned as JSON with a data URI or as raw SVG.

Instructions

[Dynamic Media] Generate a status badge SVG (label | message) in flat or flat-square style 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": {
      "label": "<label>",
      "message": "<message>"
    },
    "name": "caelara_media_badge_shield_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoMessage background color (default 2ea44f) (hex, with or without #)
labelYesLeft label
styleNoflat (default) or flat-square
formatNojson (default, includes svg + data URI) or svg (raw image/svg+xml)
messageYesRight message
label_colorNoLabel background color (default 555555) (hex, with or without #)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that the tool calls an external endpoint (https://media.caelaralabs.com) and reports p50/p95 latency, which is genuine added context. However, it says nothing about side effects, auth requirements, idempotency, rate limits, or what the json-vs-raw response contains beyond the one-word purpose line.

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?

Front-loaded with purpose first, then performance and endpoint in compact sentences. The benchmark clause and date are slight filler for an agent's decision-making but occupy minimal space.

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 simple SVG generator with fully documented parameters and no output schema, the description plus schema cover what an agent needs to invoke it. The missing piece is any hint of error behavior or response shape when format=svg versus json.

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 the schema already documents all six parameters including defaults and formats. The description only echoes the label|message pairing and the flat/flat-square styles, adding essentially no syntax or semantic detail beyond the schema.

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+resource: "Generate a status badge SVG (label | message) in flat or flat-square style," which is clearly distinct from siblings like qr_code_svg_builder or avatar_initials_svg. It never names a sibling or states scope against them, so it stops short of 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 Guidelines3/5

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

The badge-generation framing implies when to use it (shields-style status badges), but there is no explicit when-to-use/when-not guidance and no alternative named among the many media-composite siblings. Usage is inferred from the purpose, not stated.

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