Realtap

Badge and widget snippet

get_embed_snippet

Read-onlyIdempotent

A live SVG badge and an iframe widget for a stake pool, DRep or token: the URLs, Markdown and HTML to paste into a README, a website or a forum post. Checks that the subject exists.

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": {
      "subject": "<subject>",
      "id": "<id>"
    },
    "name": "get_embed_snippet"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Pool id (pool1… or 56 hex), DRep id (drep1… or 56 hex) or token unit (policy id + asset name in hex).
`color`	No	Badge colour: green, yellow, red, blue, orange, grey, brand, or 3 or 6 hex digits. Default: the colour the figure earns.
`label`	No	Replaces the left-hand text of the badge (printable ASCII, at most 30 characters).
`style`	No	Badge style: flat, flat-square or for-the-badge.	flat
`theme`	No	Theme of the iframe widget: dark, light or auto.	dark
`metric`	No	What the badge shows. Pool: return, luck, blocks, saturation, stake, delegators, pool. DRep: votes, participation, power, delegators, drep. Token: price, price-ada, change, token. Default: the identity badge (pool, drep or token).
`subject`	Yes	What the badge is about: pool, drep or token.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds two things beyond them: the badge is 'live' (dynamically rendered, not a static snapshot) and the call 'checks that the subject exists', foreshadowing failure on a bad id. It stops short of describing caching, refresh cadence or the shape of the returned snippet object.

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?

Two sentences, front-loaded with the deliverable, then the artifact list given as a compact colon series. No filler, and the existence-check caveat is placed last where it belongs.

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 7 parameters, no output schema and rich annotations, the description covers what the tool produces and that it validates the subject. The remaining gap is the return shape — whether one call yields badge URL, widget URL, Markdown and HTML together — which no output schema documents.

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 every parameter including subject, id, metric, color, label, style and theme is already documented with enums, defaults and limits. The description only echoes the pool/DRep/token subject axis and adds no format or interaction detail, so the baseline 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?

States a concrete resource (an SVG badge and iframe widget) plus the exact artifacts returned (URLs, Markdown, HTML), which makes it unmistakable against data-returning siblings like get_pool, get_drep or get_token. An agent can tell in one reading that this produces embeddable snippets, not entity data.

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 destination contexts ('a README, a website or a forum post') imply when to reach for it, but there is no explicit when-not and no named alternative such as get_pool or get_stake_pool for agents that want raw figures instead of a badge. Usage is inferable rather than stated.

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

All Realtap tools Inspect

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

Need Help?