Skip to main content
Glama

Platform coverage

get_coverage
Read-onlyIdempotent

Which hiring platforms (ATS) are covered and whether they work: status (live, blocked, no live deployments, no connector, no tenants), career sites, open jobs and last successful crawl. required is true for platforms on the challenge list of 78 and false for additional ones. Not for finding jobs; use search_jobs.

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_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly platforms with this status; omit for all platforms.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"Only platforms with this status; omit for all."New value: +"Only platforms with this status; omit for all platforms."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so safety is covered; the description adds real semantic context on top: the five possible status values and the meaning of the `required` flag (true for platforms on the challenge list of 78). It does not explain why a platform might be 'blocked' or what 'no connector' implies operationally, which is the main remaining behavioral 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?

Content is dense and front-loaded: what is covered, the status vocabulary, the `required` semantics, then the exclusion. The line breaks and parenthetical enum dump make it slightly scannable-awkward, but there is no filler sentence.

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?

With an output schema present, return values needn't be spelled out, and the description still names the salient fields plus the meaning of `required`. For a single-parameter read-only tool it is nearly complete; only the practical meaning of blocked/no-connector states is left unexplained.

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% and the single `status` parameter already documents its enum and default, so the schema carries the burden. The description repeats the status vocabulary but adds no syntax or filtering nuance beyond what the schema states.

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 concrete verb-and-resource ('which hiring platforms (ATS) are covered and whether they work') and enumerates the returned fields: status values, career sites, open jobs, last successful crawl. It also explicitly distinguishes itself from the sibling search_jobs ('Not for finding jobs'), so an agent can route without opening the schema.

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?

It gives an explicit exclusion plus the alternative ('Not for finding jobs; use search_jobs'), which is exactly the kind of negative routing guidance that helps. It doesn't address when to pick this over other non-job siblings such as index_stats, but the primary confusion risk is covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources