Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp

Get a queued job's result

get_job
Read-only

Use this when keyboard_walk, simulate_condition, screen_reader_transcript or check_page_alt_text returned a job id instead of a result — never abandon the check, collect it here. Pass the job id the tool returned; if it is still running, call again in a few seconds. The payload is identical to the one the tool would have returned inline — the same fields, the same caps, the same void handling — so nothing has to be parsed differently because a page was slow. The per-response options below are read from this call rather than from the queued run, so a job can be collected with more detail than it was asked for without paying for a second browser run. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNokeyboard_walk and simulate_condition: return every selector each finding carries instead of the first 5, from the stored result. No page is loaded and nothing is charged, so this is how a truncated selector list is resolved.
jobIdYesJob id returned by the tool that queued it.
websiteYesThe website domain the job belongs to, e.g. "example.com".
includeRingNokeyboard_walk only: include the tab ring, one entry per stop. Off by default.
includeNodesNoscreen_reader_transcript only: include the per-announcement array with node ids and roles. Off by default; its text duplicates the transcript.
includeMeasurementsNosimulate_condition only: include the raw per-condition measurements. Off by default.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as read-only and non-destructive, but the description adds important behavior beyond that: per-response options are read at collection time rather than at queue time, a job can be collected with more detail without a second browser run, and no page is loaded or charged.

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?

The first sentence front-loads the critical routing information, and every following sentence contributes non-obvious behavioral detail. There is no wasted prose; the description is dense but well organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers trigger conditions, polling behavior, response equivalence, collection-time option semantics, and cost/charge implications. Because the payload is stated to be identical to the queued tool's inline result, the absence of an output schema is not a gap.

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 schema fully documents all six parameters with a 100% coverage, so the baseline is 3. The description adds meaning by explaining the jobId contract and clarifying that the boolean per-response options are evaluated when the job is collected, which gives the agent a better mental model of how the parameters work.

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 action and resource: collect the stored result of a queued job. It names the exact four tools that can return a job id and clearly distinguishes this tool from inline result delivery.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: when keyboard_walk, simulate_condition, screen_reader_transcript, or check_page_alt_text returned a job id instead of a result. It also tells the agent to retry after a few seconds if the job is still running and explains that no different parsing is needed because the payload is identical to inline.

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

All Inclusify Accessibility toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

The descriptions do exceptional cross-referencing work, explicitly separating near-neighbor pairs (add_website vs add_domain, list_alt_findings vs check_page_alt_text, plan_options vs billing_link, widget_status vs widget_usage). A few clusters remain that an agent could confuse without reading carefully, notably site_overview vs compliance_status (both report statement existence and scan-record state) and crawl_summary vs list_monitored_pages vs site_overview (all touch coverage numbers). Overall, distinct purposes are clearly delineated despite the large surface.

Naming Consistency4/5

All names are lowercase snake_case with strong family patterns: list_* (5 tools), add_* (3), set_* (7), plus org_* and *_history pairs. The main inconsistency is the mix of verb-led names (list_violations, set_slack_channel, start_crawl) with noun-led read names (site_overview, compliance_status, widget_usage, next_steps), but the noun-led names follow a coherent 'what it returns' vocabulary (status, summary, history, overview, rollup). Minor deviations rather than chaos.

Tool Count3/5

36 tools is heavy and sits above the 25-tool threshold where agent navigation starts to degrade, but the server covers a genuinely broad domain: website lifecycle, monitoring, four finding types, four live-audit tools, seven config setters, org rollups, billing, and CI. Most tools earn their place and none are duplicates, but several could plausibly be merged (set_slack_channel/set_slack_events/set_monitoring_settings into one notifications tool; list_violations/list_alt_findings/list_content_findings with a filter). The count is on the edge of unwieldy for an agent's tool-selection step.

Completeness3/5

The read/audit/analysis side is rich and well-covered: findings, history, live checks, org rollups, coverage, and validation all have tools. However, the write side is one-directional: add_monitored_pages is explicitly add-only, and there is no remove_website, remove_domain, or remove_monitored_pages, so teardown and 'stop monitoring this page' requests hit dead ends that the descriptions acknowledge belong to the panel. Statement content writing and widget installation are also panel/browser-only by design, which is documented but still leaves those operations outside the agent's reach.

Resources