Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_status

Checks whether your Cotlet.dev account, credits, and Ashby connection are ready for recruiting workflows.

Instructions

Check that your Cotlet.dev account and Ashby are ready: account, credits and Ashby connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the three things inspected (account, credits, Ashby connection), which is real behavioral content. However, it says nothing about what a check returns, whether failures raise errors versus status flags, whether it is strictly read-only, or whether the credits check itself consumes anything.

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?

A single front-loaded sentence with the verb and the three checked resources, no filler, and no redundancy against the empty schema. It is appropriately sized for a zero-parameter diagnostic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of information, and it omits what the result looks like (booleans, status strings, error behavior) and what to do if a check fails. The subject matter is covered; the outcome is not.

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 nothing needs explaining and the baseline is 4. The description correctly presents this as a no-argument check rather than implying hidden inputs.

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?

The description gives a specific verb ('Check') and enumerates the resources inspected: account, credits, and the Ashby connection. It is clearly distinguishable from the browser-action siblings (click, open, read, type) as a readiness/diagnostic tool. It stops short of a crisp one-line statement of purpose, but the intent is unambiguous.

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 phrasing 'Check that ... are ready' implies this is a prerequisite/health check to run before other operations, but the description never states when to call it, how often, or whether it should precede the ashby_* action tools. Usage is inferable rather than stated.

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