Skip to main content
Glama

Social share card check

bpj_social_card_check
Read-onlyIdempotent

Check share-card copy, the image URL scheme and image proportions.

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": {
      "title": "<title>",
      "description": "<description>",
      "image": "<image>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "bpj_social_card_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes
titleYes
widthYes
heightYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 profile is covered. The description adds which aspects are validated, but says nothing about what constitutes a failure, what thresholds apply to image proportions, or which URL schemes are acceptable — presumably HTTPS/absolute.

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?

A single front-loaded sentence with no padding, which is efficient. However, the brevity shades into under-specification for a five-parameter validation tool, so it is terse rather than genuinely well-structured.

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

Completeness2/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 is the only place the agent can learn the result shape — yet it never says whether the tool returns a pass/fail, per-field diagnostics, or suggested fixes. For a five-required-parameter validator, that leaves a real gap.

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 0%: the five required parameters carry only generic titles ("Share title", "Image width in pixels"). The description could have explained the copy-length expectations or the target aspect ratio that width/height are checked against, but instead it only restates the categories it validates.

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 specific verb ("Check") plus three concrete targets: share-card copy, the image URL scheme, and image proportions. That is enough to separate it from nearby siblings such as bpj_image_alt_check or bpj_responsive_image_check, which test different image attributes.

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 scope of the check implies when it applies (validating social share-card metadata before publishing), but there is no explicit when-to-use, no prerequisites, and no mention of any alternative or complementary tool. The agent must infer the trigger condition.

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.