Openings

Check job coverage

get_job_coverage

Read-onlyIdempotent

Report how many live roles the index holds for each country and how recently they were posted. Use it to set expectations before asking a candidate for anything, or to judge whether preparation is worth running; use search_jobs instead to see the roles themselves. Reads the index already on hand and never crawls.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`countries`	Yes	Two-letter codes to report coverage for, such as IN or US

Output Schema

TableJSON Schema

Name	Required	Description	Default
`countries`	No	Per-country live and recent role counts
`snapshotUpdatedAt`	No	When the index this answer came from was last refreshed

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / countries / description

Added value: +"Two-letter codes to report coverage for, such as IN or US"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "countries": {
+      "description": "Per-country live and recent role counts",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "snapshotUpdatedAt": {
+      "description": "When the index this answer came from was last refreshed",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond those hints: it reads an index already on hand and never crawls, which sets cost and side-effect expectations. No contradiction with annotations.

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 concise sentences cover the core function, usage context, an alternative tool, and a behavioral caveat. No filler or redundant repetition of schema or annotation information.

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?

For a one-parameter, read-only reporting tool with an output schema, the description supplies use cases, sibling differentiation, and a clear no-crawl guarantee. Everything an agent needs to decide when to call it and what it will do is present.

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%: the single countries parameter is fully documented with type, pattern, min/max, uniqueness, and an example. The description adds little beyond tying 'each country' to that parameter, so baseline 3 is appropriate.

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 ('Report'), resource ('live roles the index holds'), grouping ('for each country'), and a recency dimension ('how recently they were posted'). It also differentiates from the sibling search_jobs, so an agent can tell at a glance what this tool does and what it does not.

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 tells the agent when to use the tool ('set expectations before asking a candidate', 'judge whether preparation is worth running') and names the alternative ('use search_jobs instead to see the roles themselves'). This is direct when/when-not guidance, not implied.

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

All Openings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.