Skip to main content
Glama
Sign In

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Make a barcode

create_barcode
Read-onlyIdempotent

Make a Code 128 or EAN-13 barcode as a PNG image, or as SVG text with format svg. code128 takes 1 to 80 printable ASCII characters; ean13 takes 12 digits, or 13 with the check digit, and the answer carries the check digit. The image is the bars alone, with no digits under them. No API key, no account and no sign up.

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": {
      "type": "<type>",
      "data": "<data>"
    },
    "name": "create_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe text or the digits to encode.
typeYescode128 for text, ean13 for a 12 or 13 digit article number.
formatNopng (default) answers the image; svg answers the SVG text in barcode_svg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), and the description adds genuinely useful context beyond them: no API key or account needed, and the output image is bars alone with no human-readable digits beneath. It stops short of explaining how the PNG is delivered (content block vs field), which is the one remaining behavioral question.

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?

Three front-loaded sentences covering output format, per-type input rules, and rendering details, with almost no filler. The closing 'no API key, no account and no sign up' is mildly promotional but does convey the auth requirement.

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?

With no output schema, the description carries the burden of describing returns and mostly does: PNG vs SVG text in barcode_svg, and the no-digits rendering detail. Only the shape of the PNG response is left implicit, a small gap for a three-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the exact character range for code128, the 12-vs-13-digit ean13 rule, and the fact that the returned barcode carries a computed check digit. That check-digit behavior is not inferable from the schema alone.

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 resource plus the two supported symbologies and output formats, so the agent knows exactly what the tool produces. It does not explicitly contrast with the sibling create_qr_code, but 'barcode' with named symbologies is specific enough to differentiate on its own.

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?

Gives concrete input constraints per symbology (code128 = 1-80 printable ASCII; ean13 = 12 or 13 digits) and how to select SVG, which effectively tells the agent which type to pick for text vs numeric article numbers. It offers no explicit when-to-use or when-not guidance, nor any routing to alternatives such as create_qr_code.

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

All AI SENSE Free Public Tools 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