Skip to main content
Glama

Image alternative text check

bpj_image_alt_check
Read-onlyIdempotent

Check the supplied alternative text against a decorative, informative or functional image role.

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": {
      "role": "<role>",
      "alt": "<alt>"
    },
    "name": "bpj_image_alt_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
altYes
roleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond purpose: it does not say what the check returns (pass/fail vs. issue list), what rule set it applies, or the notable expectation that a decorative role should have blank alt. No contradiction with annotations, but little behavioral disclosure.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the phrase 'against a ... role' is slightly compressed and could be tightened into clearer validation language.

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 and two required parameters, the description should explain what a returned check result looks like and how the role alters the verdict. Neither is covered, so an agent knows what to send but not what to expect back or how to interpret a failure.

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 reported as 0%, and no parameter carries an enum, so the description genuinely adds the three role values (decorative, informative, functional) that the schema does not enumerate. However it does not explain what alt content is expected per role or that blank alt is legitimate only for decorative, so meaning is only partially extended.

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: 'Check the supplied alternative text' against an image role. The subject (alt text) is distinct from sibling accessibility checks such as form label or link label checks, so an agent can tell what it validates. It stops short of explicitly contrasting itself with the adjacent image tools (responsive_image_check, image_frame_fit).

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: supply alt text plus a declared image role and it will be validated against that role. There is no explicit when-to-use/when-not-to-use guidance, no statement of prerequisites (e.g. that a role must already be decided), and no routing to alternative tools for other image or accessibility checks.

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.