Skip to main content
Glama

Caelara Labs Dynamic Media

badge_shield_generator

Generate a status badge SVG (label | message) in flat or flat-square style

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": "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 observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about side effects (none expected for a pure generator), whether output is a raw SVG string or data URI, or how the `format` parameter affects the response. The one sentence describes the artifact, not how the tool behaves.

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; the core capability is stated immediately. It is terse to the point of omission, but nothing present is wasted.

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 a stateless single-artifact generator with fully documented parameters, the description covers the essential capability, and the `format` parameter compensates for the absent output schema by explaining the return shape. However, the lack of any behavioral or usage context leaves the agent to infer too much about when this badge tool is appropriate.

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, including color defaults, style options, and format output behavior. The description only restates the style choices already in the schema and adds no new meaning such as valid format interactions or defaulting rules.

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 and resource ("Generate a status badge SVG") and even conveys the visual layout ("label | message") and available visual styles. It does not distinguish itself from siblings such as avatar_initials_svg or qr_code_svg_builder, which is the only thing keeping it from 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 when-to-use or when-not-to-use guidance, no mention of alternatives, and no stated preconditions or constraints. An agent must infer entirely from the tool name and sibling list which badge generator to pick.

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