Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_answer

Retrieve a single demographic survey response by ID from Greenhouse ATS. Read-only; use list_answers or list_answers_for_application to find IDs.

Instructions

Get a single demographic survey response by ID. Read-only.

To find IDs: list_answers or list_answers_for_application.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "answer_id": "<answer_id>"
    },
    "name": "get_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
answer_idYesDemographic answer ID — get from list_answers

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / answer_id / description
      Added value: +"Demographic answer ID — get from list_answers"
  2. Addedv0.3.4

TDQS

A4.2/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 burden. It does disclose the key behavioral trait ('Read-only'), which is valuable. However, it says nothing about not-found/error behavior or how missing IDs are handled, which would benefit an agent calling with a user-supplied ID.

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?

Two sentences, purpose front-loaded, followed by the practical ID-sourcing tip. No filler; every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the single parameter is fully documented. The only unaddressed edge is error/not-found behavior, a minor gap for a read getter.

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 the schema already documents answer_id and its type. The description reinforces 'by ID' and names the ID source, but adds little beyond the schema. Baseline 3 when the schema does the heavy lifting.

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?

States a specific verb (Get), resource (a single demographic survey response), and scope (by ID, single). This clearly distinguishes it from the sibling list tools list_answers and list_answers_for_application that return multiple responses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the two alternatives (list_answers, list_answers_for_application) that supply the required ID, giving a concrete condition for their use. For a single-param getter, this is the needed guidance.

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