Skip to main content
Glama

Attify

Badge embed code

get_badge_embed
Read-onlyIdempotent

The code for your live Attify badge, once a program's score is public: one line for a website (a plain link to your profile, then the script that draws the current badge and its hover card), the image for email signatures and READMEs, and the badge's addresses. Before that, what publishing still needs Needs sign-in to Attify; reads only.

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": "get_badge_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
themeNo
programNoIts id, profile slug or product name; omit when you have one.
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the tool only yields useful output once a score is public, and it requires sign-in to Attify. That gating behavior is not derivable from the annotations, though the sentence expressing it about the pre-public state is mangled.

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 output enumeration is front-loaded and informative, but the final sentence is a run-on with a duplicated verb ('needs Needs') that reads as corrupted text and undercuts an otherwise tight definition. The 'reads only' tail merely restates readOnlyHint, which is wasted space given annotations.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return shape, and it does partially by listing the three deliverable forms, but it does not say how they are structured in the response. It also does not explain what happens when `program` is omitted, even though the schema explicitly allows omission 'when you have one'.

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

Parameters2/5

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

Schema description coverage is only 25% — just the `program` property is documented — and the description mentions no parameters at all. The `size`, `theme` and `variant` enums (footer/pricing/hero/email, light/dark/auto, full/compact/chip) convey rough intent by their values, but defaults and the effect of each choice, especially how `size` interacts with `variant`, are left entirely unexplained.

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?

The description names a concrete artifact — embed code for a live Attify badge — and enumerates what comes back (a website line with link plus drawing script and hover card, an email/README image, and the badge's addresses). That is specific enough to distinguish it from sibling read tools like get_program_status or get_standard, though it never explicitly contrasts with them.

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?

A real precondition is stated ('once a program's score is public'), which is the key gating condition for using this tool. However, the follow-on clause 'Before that, what publishing still needs Needs sign-in to Attify' is garbled and never names which tool to use when the score is not yet public, so the alternative path is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources