Skip to main content
Glama

Ashby

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ashby Get Candidate

ashby_get_candidate
Read-onlyIdempotent

Get full candidate profile by ID. Returns contact info, resume, interview history, and current application status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesAshby API key
candidateIdYesAshby candidate ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCandidate ID
nameNoCandidate full name
emailNoCandidate email address
resumeNoCandidate resume content or URL
applicationsNoList of applications from this candidate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "applications": {
+      "description": "List of applications from this candidate",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Application ID",
+            "type": "string"
+          },
+          "jobId": {
+            "description": "Job ID applied for",
+            "type": "string"
+          },
+          "stage": {
+            "description": "Current application stage",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "email": {
+      "description": "Candidate email address",
+      "type": "string"
+    },
+    "id": {
+      "description": "Candidate ID",
+      "type": "string"
+    },
+    "name": {
+      "description": "Candidate full name",
+      "type": "string"
+    },
+    "resume": {
+      "description": "Candidate resume content or URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-ashby-api-key",
+    "candidateId": "cand_12345"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds detail on return contents (contact info, resume, interview history, status), complementing rather than contradicting annotations.

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?

The description is two sentences: the first succinctly states the purpose, the second lists return contents. No unnecessary words, front-loaded with key information.

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?

Given the tool's low complexity, 2 required parameters, existing output schema, and annotations, the description sufficiently conveys purpose and return data. It omits error handling or auth details, but these are covered by the schema and annotations.

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?

Schema coverage is 100% and both parameters are well-described in the schema. The description does not add additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 explicitly states 'Get full candidate profile by ID' and lists specific return contents (contact info, resume, interview history, status). It clearly identifies the verb, resource, and scope.

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 description implies usage when a specific candidate ID is known, but does not explicitly mention when to avoid this tool or provide alternatives (e.g., use ashby_list_candidates for listing).

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

All Ashby toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources