Skip to main content
Glama

Get embed badges

toolfound_get_badge
Read-onlyIdempotent

Get the three copy-paste badge embed snippets for a Toolfound listing ('live on Toolfound', 'verified', 'top 3 this week' variants). Badges are optional and earned, they deep-link to the listing with varied anchor text, and the embedder chooses the rel attribute freely. Listing status is never conditioned on embedding a badge.

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": {
      "slug": "<slug>"
    },
    "name": "toolfound_get_badge"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug of the listing that needs embed snippets, taken from its toolfound.com URL. The badges link back to this listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Slug of the listing to get badges for."New value: +"Slug of the listing that needs embed snippets, taken from its toolfound.com URL. The badges link back to this listing."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's job is lighter and it delivers: it fixes the exact payload (three snippets), explains they deep-link with varied anchor text, and explicitly leaves the rel attribute to the embedder. The 'badges are optional and earned' and 'status never conditioned on embedding' guarantees are genuinely non-obvious behavioral facts an agent could not get from annotations. It stops short of showing snippet shape or noting any length/format constraints, which keeps it off a 5.

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?

Purpose is front-loaded in the first clause with the variant list in a tight parenthetical, and the follow-up sentence packs only policy-bearing facts. The single long sentence is dense but every clause carries information; a light split for readability would improve it marginally.

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?

For a one-parameter, read-only snippet generator with full schema coverage and complete annotations, this is sufficient: it says what is returned, how the snippets behave, and that embedding has no effect on listing status. No output schema exists, and the description covers the return content itself, so nothing critical is missing.

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% and the slug parameter is already documented as coming from the listing's toolfound.com URL. The description only reinforces this with 'The badges link back to this listing,' adding little meaning beyond the schema, which is the expected baseline when the schema carries the burden.

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 — 'Get the three copy-paste badge embed snippets for a Toolfound listing' — and even enumerates the three variants, so an agent knows exactly what comes back. It does not name or contrast any sibling (e.g., toolfound_get_verified_board or toolfound_verify_submission), so an agent must infer the boundary from the word 'embed snippets' alone.

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?

Usage is implied rather than stated: you call it when a listing owner wants badge HTML, and the description clarifies badges are 'optional and earned' and that 'listing status is never conditioned on embedding a badge.' That is useful policy context, but there is no explicit when-to-use trigger, no prerequisites (e.g., must the listing be verified/live first?), and no named alternative for adjacent needs.

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