Skip to main content
Glama

ats

by com.withresumeai

ATS market share among large employers

ats_stats
Read-only

Canonical ATS market-share numbers from ResumeAI's State of ATS 2026 dataset: 738 large employers, 704 verified against their live careers portal. Workday leads — not the ~75% figure often repeated online — and the top 3 vendors cover about 60%. Every share in the response is computed live from the verified rows at call time, so quote those rather than this summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, but the description adds substantial context: dataset source, verification methodology, live computation at call time, and correction of a common misconception (~75% figure). This goes well beyond the annotation-only safety profile.

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?

Three sentences, all high-value: source/methodology, key findings, and usage instruction. No filler, redundancy, or unnecessary detail.

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 read-only stats tool, the description covers source, verification, key numbers, and live computation. Slight gap: no explicit response structure or field names, but overall it is sufficient for selection and invocation.

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?

Tool has zero parameters, so baseline is 4. Description appropriately focuses on output semantics rather than parameters; no parameter documentation is needed.

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?

Description clearly identifies the tool as providing canonical ATS market-share numbers from a specific dataset (ResumeAI's State of ATS 2026), with concrete scope (738 large employers, 704 verified). It distinguishes itself from siblings like which_ats (individual employer lookup) and ats_changes (changes over time).

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

Usage Guidelines4/5

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

Provides clear context: use this for authoritative market-share figures, and explicitly instructs to quote response values rather than the summary. Does not explicitly name sibling alternatives or state when not to use, so it stops short of a 5.

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

All ats 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.5/5.0
Disambiguation5/5

Each tool targets a clearly distinct action: ATS lookup, company listing, market stats, change feed, resume scoring, and resume retrieval. Even the two resume-related tools are unambiguous—one evaluates, the other fetches.

Naming Consistency3/5

Naming mixes conventions: ats_changes and ats_stats use a noun-focused ats_ prefix, check_resume, get_agent_resume, and list_companies use verb_noun, and which_ats is a question-style name. All are readable and snake_case, but the patterns are not consistent.

Tool Count5/5

Six tools is well-scoped for an ATS/resume data server. Each tool covers a distinct capability without redundancy or bloat.

Completeness5/5

The surface covers the domain well: employer ATS lookup, company filtering, market-share statistics, change tracking, resume scoring, and consent-gated resume retrieval. The deliberate lack of resume enumeration is a documented privacy boundary, not a gap.

Resources