Skip to main content
Glama

Off the Floor Nurse Jobs

List nurse job roles

list_roles
Read-onlyIdempotent

List the role families on Off the Floor (https://offthefloornurse.com) with how many listings each has and how many are fully remote, plus listing counts by license (RN, LPN, NP) and 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

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description wisely spends its budget on data-lifecycle semantics instead: data is re-read from employer career sites on rebuild, each result carries data_updated_at, listings are retained when a feed fails, and each carries last_seen before being dropped after several days of downtime. That is real context an agent needs to interpret counts, though there is no detail on cost, refresh cadence, or rate limits.

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?

The first sentence front-loads the payload and what follows supports interpreting it, but the middle sentence naming the four ATS vendors (Workday, Greenhouse, Lever, Ashby) is incidental detail that does not change how an agent calls the tool. The retention sentence is dense but earns its place by explaining why counts can lag reality.

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 zero parameters, no output schema, and a small sibling set, the description covers what is returned (breakdowns by role, license, remoteness, work mode) and the freshness metadata accompanying them. It stops short of describing the response shape or whether an overall total is included, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline applies and the surrounding prose instead clarifies what the returned dimensions mean.

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?

States a specific verb and resource plus the exact dimensions returned: role families with listing counts, remote counts, counts by license (RN, LPN, NP) and by work mode. The phrase 'Counts only' cleanly separates it from a job-listing search tool, though it never names a sibling to route away from.

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?

Usage is implied rather than stated: 'Counts only, from the board's current data file' signals an aggregate/overview call and the freshness paragraph hints at when staleness matters, but there is no explicit when-to-use-this-vs-search_jobs or employer_counts guidance, and no exclusions.

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