Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_audit_accessibility

Audit image alt-text against WCAG 2.2 and scan post text for content warning triggers to help ensure accessible, sensitive posts.

Instructions

Audit alt-text against WCAG 2.2 accessibility standards and detect content warning (CW) triggers for sensitive posts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_audit_accessibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_textNoImage alt-text description to audit.
platformNoTarget social platform (twitter, bluesky, mastodon, threads, linkedin).twitter
post_textNoAccompanying post body to scan for content warnings (CW).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It states the standard applied (WCAG 2.2) and the second detection task, but says nothing about what the audit reports (pass/fail, issue list, severity), whether findings are advisory only, or whether any side effects occur. For a tool with zero annotation coverage this is a significant gap.

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 efficiently worded sentence with no filler, and the WCAG standard is front-loaded. Bundling two capabilities into one clause without clarifying whether they run together costs it a point.

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 should indicate what an audit returns, and it does not. For a three-parameter, two-function analysis tool with no annotations and no return definition, the definition is minimally adequate but leaves the agent guessing about results.

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%, so the schema already documents all three parameters, making 3 the baseline. The description adds nothing beyond them — notably it never explains what the 'platform' parameter changes, which is the one parameter whose effect an agent could plausibly get wrong.

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 resource ('Audit alt-text against WCAG 2.2 accessibility standards') plus a second, clearly named capability ('detect content warning (CW) triggers'). It is easy to distinguish from all listed siblings, none of which handle accessibility or CW checking, though the relationship between the two functions is not spelled out.

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: the audit framing suggests checking alt-text/post text before publishing. There is no explicit statement of when to call this versus alternatives, no prerequisites, and no guidance on what happens if only one input is supplied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.