Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_degrees

Retrieve degree types (Bachelor's, Master's, PhD) and their IDs for adding education records. Read-only, supports pagination.

Instructions

List degree types (Bachelor's, Master's, PhD, etc.). Read-only.

Resolves degree names to IDs (degree_id) for add_education. Each item is a custom field option with id and name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPass next_cursor from the previous response to get the next page
paginateNo'single' for one page, 'all' to auto-fetch every pagesingle
per_pageNoResults per page (max 500)
force_refreshNoBypass cache and fetch fresh data

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pass next_cursor from the previous response to get the next page",
+  "title": "Cursor"
+}
    • addedInput schema / properties / force_refresh / description
      Added value: +"Bypass cache and fetch fresh data"
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "title": "Page",
-  "type": "integer"
-}
    • addedInput schema / properties / paginate
      Added value: +{
+  "default": "single",
+  "description": "'single' for one page, 'all' to auto-fetch every page",
+  "title": "Paginate",
+  "type": "string"
+}
    • addedInput schema / properties / per_page / description
      Added value: +"Results per page (max 500)"
  2. Addedv0.3.4

TDQS

A3.6/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 correctly declares 'Read-only', which is the single most important behavioral trait for a list tool. It also describes the return structure ('Each item is a custom field option with id and name') and hints at caching with 'force_refresh'. However, it does not mention pagination behavior (cursor, paginate, per_page) or rate limits, which are relevant for a tool with 4 parameters. The disclosure is adequate but not rich.

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 description is three sentences, front-loaded with the core purpose and read-only nature, followed by the specific use case and return format. There is no filler. It could be slightly tighter by merging the usage and return structure, but it is efficient and well-structured.

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?

For a read-only list tool with 4 optional parameters and a full output schema, the description covers the essential purpose, safety, and return shape. However, it omits pagination guidance despite the tool having cursor/paginate/per_page params, and does not distinguish from 'list_board_degrees'. Given the complexity of the sibling set and the presence of pagination knobs, it is adequate but incomplete.

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 description coverage is 100%, so all four parameters (cursor, paginate, per_page, force_refresh) are fully documented in the schema. The description adds no parameter-specific information beyond what the schema provides. Per the rubric, the baseline is 3 when the schema does the heavy lifting, and the description does not compensate further.

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 clearly states a specific verb and resource: 'List degree types (Bachelor's, Master's, PhD, etc.)'. This distinguishes it from most siblings. However, it does not explicitly differentiate from the very similarly named 'list_board_degrees' in the sibling list, which likely serves a similar purpose in a different context (board vs. general). A note about that distinction would earn 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 Guidelines4/5

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

The description explicitly states the primary usage: 'Resolves degree names to IDs (degree_id) for add_education.' This is a strong, actionable usage guideline that tells the agent exactly why and when to call this tool. It lacks explicit when-not-to-use guidance or mention of the sibling 'list_board_degrees', but the context provided is clear and directly useful.

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