Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_avatar_initials_svg

Generate a deterministic initials avatar SVG from a name, with background and text colors selected to keep text accessible. Supports custom size and shape.

Instructions

[Dynamic Media] Generate a deterministic initials avatar SVG with an accessible text color 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": {
      "name": "<name>"
    },
    "name": "caelara_media_avatar_initials_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color (default derived from the name) (hex, with or without #)
fgNoText color (default chosen for contrast) (hex, with or without #)
nameYesPerson or company name
sizeNoSize in px (24-1024, default 128)
shapeNocircle (default), rounded or square
formatNojson (default, includes svg + data URI) or svg (raw image/svg+xml)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/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 it does disclose real behavior: output is deterministic, the text color defaults to an accessible contrast choice, and the call goes out to https://media.caelaralabs.com with measured p50/p95 latency. It omits auth requirements, rate limits, failure modes, and whether defaults are recomputed per call — meaningful gaps for a network-backed tool.

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

Conciseness3/5

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

The purpose clause is front-loaded and compact, but the sentence runs on because a period is missing between 'text color' and 'Measured p50', and the benchmark citation with an exact date and hostname is over-precise filler relative to the decision it supports. Nothing egregious, but it is not tight.

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 six-parameter generator with one required field, no annotations, and no output schema, the definition is largely sufficient: the schema covers every parameter including the json-vs-raw-svg return form, and the description adds determinism, contrast defaults, and network scope. Remaining gaps are auth and error behavior, which are secondary for a simple content generator.

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 all six parameters are already documented, and the description only echoes two of them indirectly via 'accessible text color' (the fg default) and 'deterministic' (name-derived bg). It adds no syntax, interaction, or edge-case detail beyond what the schema states, so the 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?

States a specific verb and artifact: 'Generate a deterministic initials avatar SVG with an accessible text color.' The resource ('initials avatar') naturally separates it from siblings producing QR codes, OG images, or badges. It never explicitly names a sibling or a boundary, 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 Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use, and no mention of alternatives among the many other media generators. The only contextual cues are a latency figure and an endpoint URL, neither of which helps an agent choose this tool over another.

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