Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_current_offer

Retrieve the current offer for a Greenhouse application to view the active version or check if one exists; returns 404 when no offer is present.

Instructions

Get the current (latest version) offer for an application. Read-only.

Returns 404 if the application has no offer. To find application_id: search_candidates_by_name → list_applications(candidate_id=...) → match the application to the job.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_current_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesGreenhouse application ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / application_id / description
      Added value: +"Greenhouse application ID"
  2. Addedv0.3.4

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose two meaningful traits: the operation is read-only and it returns 404 when the application has no offer. That error semantics is genuinely useful, but it omits permission/scope requirements and whether non-approved offer versions are included in 'current'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and read-only trait are front-loaded, and the follow-up sentences add ID-discovery and error context without padding. The arrow-chain workflow is terse and slightly cryptic, and 'match the application to the job' is a bit vague, keeping it from a 5.

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 no explanation, and the description covers purpose, error behavior, and ID discovery. It is nearly complete for a simple one-parameter read tool, with only alternative-tool routing and permission scoping left unaddressed.

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?

Schema coverage is 100%, so the parameter is already documented, but the description adds real value by explaining the retrieval workflow for obtaining application_id rather than just restating it. That goes beyond the schema's 'Greenhouse application ID' label.

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?

States a specific verb and resource (get the current/latest offer for an application) and clarifies the version semantics with 'current (latest version)'. It does not name or differentiate itself from the sibling get_offer or list_offers_for_application, so it falls short of a 5.

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?

It provides actionable context by explaining how to obtain application_id (search_candidates_by_name → list_applications → match) and notes the 404 case. However, it never says when to use this over the sibling get_offer (which likely takes an offer_id) or list_offers_for_application, leaving the alternative selection implicit.

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