Skip to main content
Glama

Share image preview

toolfound_share_preview
Read-onlyIdempotent

Export a safe 1200×630 SVG preview from a bounded product name and tagline. Returns an evidence-bounded result and the canonical web tool URL.

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": {
      "name": "<name>",
      "tagline": "<tagline>"
    },
    "name": "toolfound_share_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProduct name printed as the headline of the preview image.
taglineYesShort supporting line printed under the name in the preview image.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Product name printed as the headline of the preview image."
    • addedInput schema / properties / tagline / description
      Added value: +"Short supporting line printed under the name in the preview image."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is covered. The description adds that the output is 'safe' and 'evidence-bounded' and includes the canonical web tool URL, but 'safe' and 'evidence-bounded' are never defined, leaving the agent guessing what sanitization or limits apply.

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?

Two sentences, front-loaded with the artifact and its dimensions, with no filler. The phrase 'evidence-bounded result' is vague jargon that does not obviously earn its place, which keeps it short of a 5.

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 an output schema present, the description need not detail return values, and it correctly notes the URL is returned. For a two-parameter, fully documented generator with rich annotations, the definition covers what an agent needs to call it correctly; only the vague qualifiers 'safe' and 'evidence-bounded' remain unexplained.

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 description coverage is 100% with only two required parameters, so the schema already explains that name is the headline and tagline is the supporting line. The description's 'bounded' hints at the minLength/maxLength limits already stated in the schema, adding no new meaning such as truncation or escaping behavior.

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 gives a specific verb and artifact: 'Export a safe 1200×630 SVG preview' from a name and tagline, so an agent knows exactly what is produced. It does not distinguish itself from any sibling, but no sibling in the listed set performs image generation, so the ambiguity risk is low.

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 by the tool's nature (supply a product name and tagline, receive a share image), but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. No alternatives are named, and it does not say whether this belongs in a launch, listing, or distribution workflow despite siblings covering those areas.

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