Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_scorecard

Retrieve a single interview scorecard by ID to view interviewer feedback, ratings, answers, notes, and overall recommendation. Use IDs from application scorecards.

Instructions

Get a single scorecard by ID. Read-only.

Returns the interviewer, interview, attribute ratings, question answers, notes, and overall recommendation (candidate_rating). To find scorecard IDs: list_scorecards_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": {
      "scorecard_id": "<scorecard_id>"
    },
    "name": "get_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
scorecard_idYesScorecard ID — get from list_scorecards or list_scorecards_for_application

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / scorecard_id / description
      Added value: +"Scorecard ID — get from list_scorecards or list_scorecards_for_application"
  2. Addedv0.3.4

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does declare "Read-only," the single most important safety trait for this operation. It also scopes what comes back, but says nothing about permission requirements or failure modes (e.g., a nonexistent or unauthorized scorecard ID), leaving some behavioral gaps.

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?

Front-loaded with the verb+resource and the read-only flag, then the ID source, with no filler sentences. The enumerated return fields are partly redundant given an output schema exists, which is the only mild inefficiency.

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?

A one-parameter getter with a full output schema needs little description; the ID source, scope, and read-only nature are all present. Missing only auth/error context, which is a minor gap for a simple read.

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 that scorecard_id comes from list_scorecards or list_scorecards_for_application, so the description's ID hint is largely redundant. The description is actually slightly narrower than the schema, which names both list tools.

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 and resource ("Get a single scorecard by ID") and the singular scope distinguishes it from the list_scorecards / list_scorecards_for_application siblings. An agent can route between the getter and the listers without opening either schema.

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?

It tells the agent how to satisfy the required parameter ("To find scorecard IDs: list_scorecards_for_application"), which is the main usage question for a single-record fetch. It does not state when not to use it (e.g., when you need all scorecards for an application, use the lister), so it stops short of full routing 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