Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

get_accessibility_report

Audit the current Figma selection for WCAG 2.2 sRGB relative-luminance contrast to identify accessibility issues.

Instructions

Get WCAG 2.2 sRGB relative-luminance contrast audit results for the current Figma selection.

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": "get_accessibility_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only states the metric and scope. It does not disclose whether the operation is read-only, requires an active selection, how costly it is, or what the report contains beyond 'results'.

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 zero wasted words. It puts the verb, standard, and scope in immediate view.

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?

For a zero-parameter getter with no output schema, the description covers what is returned at a high level and the selection scope. It could be stronger by noting read-only behavior or the shape of the audit results, but the core information needed to invoke it is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4; there is no parameter meaning for the description to add. The schema is empty and requires no compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get') and a highly specific resource ('WCAG 2.2 sRGB relative-luminance contrast audit results'), scoped to 'the current Figma selection'. This resource is clearly distinct from siblings like get_design_spec or get_design_tokens without needing to name them.

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 scope ('current Figma selection') and the audit purpose, but there is no explicit when-to-use/when-not-to-use guidance or named alternative. An agent can infer it is for accessibility checks, but not what to do if no selection exists or how it differs from compare_selections.

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