Skip to main content
Glama

Responsive image srcset check

bpj_responsive_image_check
Read-onlyIdempotent

Check simple HTTP image candidates for duplicate or mixed descriptors and a missing sizes attribute.

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": {
      "srcset": "<srcset>",
      "sizes": "<sizes>"
    },
    "name": "bpj_responsive_image_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizesYes
srcsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the specific defect categories inspected, which is useful, but leaves significant behavioral questions open: whether it actually fetches the candidate URLs, what it returns (issue list, boolean, message), and how it treats the legally blank sizes value. For a checker with a closed-world annotation, this is adequate but not rich.

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?

A single front-loaded sentence with no filler; the verb, scope, and the three checked conditions appear immediately. Nothing in the sentence is redundant with the title or the schema titles.

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 bears responsibility for telling the agent what comes back, and it does not — no indication of result shape, severity levels, or whether multiple findings are aggregated. It also never resolves whether HTTP candidates are actually retrieved, which matters for a tool annotated openWorldHint=false. For a two-input, required-both read checker, the definition is workable but incomplete.

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 0%, so the description must carry the semantic load, and it only partially does. It clarifies that a missing sizes attribute is a finding and that duplicate or mixed srcset descriptors are the target defects, which goes beyond the bare schema titles. However, 'mixed descriptors' is never explained (w vs x), and the schema's note that sizes may be blank is not reconciled with the tool's missing-sizes check.

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 clear verb ('Check') and a specific resource scope ('simple HTTP image candidates'), and names the exact conditions examined: duplicate descriptors, mixed descriptors, and a missing sizes attribute. That is far more specific than the title alone and separates it from siblings such as bpj_image_alt_check or bpj_image_frame_fit. It stops short of 5 because it never explicitly contrasts itself with those sibling image checks.

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 only implied: an agent can infer this is for validating srcset markup, and the word 'simple' suggests a scope limit, but there is no statement of when to prefer this over other image-related checks, no prerequisites, and no mention of when not to use it. The blank-sizes case is only hinted at by the 'missing sizes attribute' phrasing.

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.