Skip to main content
Glama

Exit Ticket Teacher Jobs

List kinds of work

list_roles
Read-onlyIdempotent

List the kinds of work on Exit Ticket (https://exitticketjobs.com) with how many listings each has and how many are fully remote, plus listing counts by work mode. Counts only, from the board's current data file. Data is re-read from employers' own career sites (Workday, Greenhouse, Lever, Ashby) when the board is rebuilt; each result gives data_updated_at. When an employer's feed does not answer we keep its listings. Each carries last_seen, the last day it was really seen, and goes once the feed has been down for several days.

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": "list_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description goes further by disclosing data provenance (Workday, Greenhouse, Lever, Ashby feeds), the presence of data_updated_at, and the stale-data policy where listings survive a failing feed and are dropped after several days. The last_seen semantics are genuinely valuable for interpreting counts. It stops short of describing the exact return shape or sort order, which keeps it below a 5.

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?

The purpose is correctly front-loaded in the first sentence, but the following two sentences are long, comma-chained, and mix freshness policy, feed behavior, and field semantics without structure. The point about counting "how many are fully remote" is delivered twice (once as a field, once as "listing counts by work mode"), which adds density without adding clarity.

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, no-output-schema tool, the description does the heavy lifting: it enumerates the returned aggregates and the freshness metadata that accompany them. What remains underspecified is what a "kind of work" actually is (job function, title family, or category) and whether the response is a single row or a list, but the omission is minor at this complexity.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter meaning is missing or contradicted.

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?

"List the kinds of work ... with how many listings each has and how many are fully remote, plus listing counts by work mode" names a concrete verb and resource and specifies the aggregate fields returned. "Counts only" implicitly separates it from search_jobs, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The "Counts only" qualifier implies this is for aggregate/tally questions rather than listing lookups, which is useful context. However, there is no explicit when-to-use, when-not-to-use, or named alternative among companies_hiring_former_teachers, employer_counts, or search_jobs, leaving the agent to infer selection.

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