Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_ui_audit

Audits Flutter and Arabic RTL interfaces for WCAG accessibility and render overflow issues, catching hardcoded left/right directions, missing image alt labels, and unwrapped Text in Row widgets.

Instructions

Bilingual Arabic RTL, WCAG Accessibility & Flutter RenderFlex Overflow Auditor (v11.0 Hypernova): catches hardcoded physical left/right directions, missing image alt labels, and unwrapped Text inside Flutter Row().

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": {
      "workspace": "<workspace>"
    },
    "name": "sqo_ui_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

C2.9/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 never states whether the audit is read-only, whether it scans the whole workspace or a subset, whether it emits a report or fails the run, or how long a large tree might take; only the detection targets are disclosed.

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?

It is a single front-loaded sentence, which is efficient, but the version branding 'v11.0 Hypernova' consumes space without helping tool selection. The defect list is the only part that earns its place.

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?

For a one-parameter audit tool with no output schema and no annotations, the description covers what is checked but not what comes back or how to act on results. Adequate to decide whether to call it, thin on what to expect afterward.

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 coverage is 100% and the single 'workspace' parameter is already documented as the workspace root directory. The description adds nothing about scope, exclusions, or path expectations, so the schema does all the work and baseline 3 applies.

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 audit domain (Arabic RTL directionality, WCAG accessibility, Flutter RenderFlex overflow) and enumerates three concrete defect classes it catches, so an agent can predict its findings. It stops short of explicitly distinguishing itself from the sibling sqo_i18n_audit, which covers adjacent localization ground.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to run this audit versus sqo_i18n_audit or the other sqo_*_audit siblings, and no preconditions such as requiring a Flutter project or Arabic locale resources. The agent must infer the trigger condition entirely from the defect list.

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

Deploy Server

Other Tools