Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_guide

Use this first to navigate Ashby screens and locate the sign-in link for jobs, candidates, interviews, and offers.

Instructions

How to work in Ashby (jobs, candidates, interviews and offers): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Ashby, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the rough return content (its screens and the sign-in link), which implies a read-only informational call. It never explicitly states that it performs no mutations, whether auth is required to reach the sign-in link, or what the agent should do with the returned guidance, leaving real ambiguity for a tool with zero annotation coverage.

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 compact sentence plus a directive, with the domain scope and the action ordered front to back. Nothing is wasted and the 'call this first' instruction lands where the agent will read it.

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 single-optional-parameter guidance tool with no output schema, the description covers what the tool covers and when to invoke it. The remaining gap is what the agent should expect back and what to do next, which is minor at this complexity.

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?

There is one optional parameter with 100% schema description coverage, so the schema already explains 'task'. The description adds no meaning beyond it. Baseline 3 applies when the schema does the work.

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?

"How to work in Ashby (jobs, candidates, interviews and offers): its screens and the sign-in link" names the resource domain and the content it returns, which distinguishes it from the action siblings (click, open, read, type). The verb is implicit (it is a guide rather than an action), so it stops short of a clean verb+resource statement, but an agent can tell what it is for.

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?

"Call this first" is explicit ordering guidance, which is exactly what an orientation tool needs and is stronger than most sibling definitions offer. It doesn't state exclusions or name the alternatives it precedes, but for a first-call guide that omission costs little.

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