Skip to main content
Glama
Sign In

Jinero

by online.jinero
OverviewDiscussionsAdmin

Svg To Data Uri Tool

svg_to_datauri
Read-onlyIdempotent

Encode an SVG (or fetched image) as a CSS-ready data: URI. Provide either raw svg or a url. Rate limit: 30 calls/min per IP.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "svg_to_datauri"
  }
}

Input Schema

NameRequiredDescriptionDefault
svgNoRaw SVG markup. Mutually exclusive with url.
urlNoPublic image URL the server will fetch.
quotesNoQuote style for the data URI (default double).
encodingNoDefaults: utf8 for SVG, base64 for raster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behaviors. The description adds valuable context by mentioning the rate limit and the ability to fetch external URLs, which goes beyond the schema. No contradiction with annotations.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core purpose, then provides input options and rate limit. Every sentence earns its place with no redundancy.

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 conversion tool with full schema coverage and no output schema, the description sufficiently covers purpose, input methods, and a critical constraint (rate limit). It does not elaborate on default behaviors, but the schema handles those.

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 covers all parameters descriptively, so the baseline is 3. The description reinforces mutual exclusivity between svg and url, but does not add deeper semantic meaning or defaults beyond what the schema already provides.

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?

The description clearly states the tool encodes an SVG or fetched image into a CSS-ready data URI, which is specific and actionable. It distinguishes from siblings like optimize_svg by focusing on encoding rather than optimization.

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 description implies usage for producing data URIs but does not explicitly compare with alternatives or state when not to use it. It provides the two input modes (svg or url) but lacks guidance on selecting this tool over siblings.

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

All Jinero toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources