Skip to main content
Glama
Sign In
Grey Ridge Jobs MCP

Grey Ridge Jobs MCP

by rezearcher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_platforms

Lists supported ATS platforms with token formats and auto-detect coverage, so you know how to address each board without network calls.

Instructions

List the ATS platforms this server supports and how to address each one (token format, whether auto-detect covers it). No network call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses 'No network call', indicating a local informational operation, and describes the returned content (token format, auto-detect coverage). It stops short of stating idempotence or auth requirements, but covers the key safety-relevant behavior.

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?

One efficient sentence, front-loaded with the main action and followed by the useful qualifiers. Nothing is wasted.

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 zero-parameter, no-output-schema informational tool, the description covers what it returns (supported platforms, token format, auto-detect coverage) and a key behavioral trait (no network call). That is sufficient for an agent to call it correctly.

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. The description correctly implies no inputs are needed, and there are no parameter semantics to explain.

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 gives a specific verb and resource: 'List the ATS platforms this server supports'. It also states what each entry contains (token format, auto-detect coverage), which distinguishes it from detect_ats and the search tools.

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 by the content: an agent would use this to discover supported platforms and addressing details before calling detection or search tools. However, there is no explicit when-to-use or when-not guidance, and detect_ats is only referenced indirectly through 'auto-detect'.

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

Deploy Server

Other Tools