Skip to main content
Glama

CountLink

by app.countlink
OverviewDiscussionsAdmin

Create a countdown badge for a README, forum post or similar

create_badge
Read-only

Create a countdown badge — a small image, not an — for places embed_on_website's iframe cannot go: a GitHub README, a forum signature, a Notion page, anywhere only plain Markdown or a bare is allowed. Shows coarse time remaining (e.g. "3d 04h left", not a live ticking clock — most places that embed images fetch and cache them server-side, so a promise of live ticking would be false) and links through to the real, precise, live countdown. Returns both a Markdown snippet and an HTML snippet; use whichever the destination accepts. Always returns the image wrapped in a link to the live countdown — never ask for or produce just the bare image, since the link is what makes this a genuine attribution rather than an untethered picture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional short name shown on the badge, e.g. "Launch" or "CFP closes".
durationYesHow long the timer runs. Accepts "25m", "1h30m", "90s", "5:00", "1:30:00", or a plain number read as minutes ("45"). A setup link or OBS overlay holds up to 99h59m59s. With start_now or embed_on_website, longer countdowns of up to 366 days are fine: "10d", "10 days", "10d 6h" or "240h".
badge_styleNoVisual style: "board" (default, dark), "minimal" (no background — blends into any page) or "light".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / duration / description
      Previous value: -"How long the timer runs. Accepts \"25m\", \"1h30m\", \"90s\", \"5:00\", \"1:30:00\", or a plain number read as minutes (\"45\"). Maximum 99h59m59s."New value: +"How long the timer runs. Accepts \"25m\", \"1h30m\", \"90s\", \"5:00\", \"1:30:00\", or a plain number read as minutes (\"45\"). A setup link or OBS overlay holds up to 99h59m59s. With start_now or embed_on_website, longer countdowns of up to 366 days are fine: \"10d\", \"10 days\", \"10d 6h\" or \"240h\"."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Despite readOnlyHint=true already indicating a non-destructive read operation, the description adds substantial behavior: output is a coarse time-remaining image, not live; it links through to the precise countdown; both Markdown and HTML snippets are returned; and the image is always wrapped in a link. This goes well beyond the 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?

Each sentence carries a distinct, necessary constraint or behavior: the use case, the coarse-time limitation, the returned snippet types, and the mandatory link wrapping. The description is dense but front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still tells the agent what to expect in return: a Markdown snippet, an HTML snippet, and an image wrapped in a link. It also covers the major edge-case behavior around caching and the prohibition against returning a bare image, making the tool fully callable.

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?

The input schema already provides full 100% descriptions for duration, label, and badge_style. The tool description adds useful output context, such as the example '3d 04h left', but it does not meaningfully expand on the parameter meanings themselves, so the baseline of 3 applies.

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 states a specific verb and resource: create a countdown badge, and clarifies it is a small image, not an iframe. It also distinguishes this tool from embed_on_website by naming the exact contexts where each is appropriate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly says when to use this tool versus embed_on_website: wherever only Markdown or a bare <img> is allowed, such as GitHub READMEs, forum signatures, and Notion pages. It also gives a meaningful exclusion by explaining that most image embeds are cached server-side, so a live ticking clock would be false.

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

All CountLink toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources