Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_schools

Look up schools and resolve names to school IDs for education records, so add_education uses accurate values. Read-only.

Instructions

List schools for education records. Read-only.

Resolves school names to IDs (school_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 page (the school list is long — use 'all' to search it by name)single
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 (the school list is long — use 'all' to search it by name)",
+  "title": "Paginate",
+  "type": "string"
+}
    • addedInput schema / properties / per_page / description
      Added value: +"Results per page (max 500)"
  2. Addedv0.3.4

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the read-only nature plus the fact that entries are custom field options shaped as id/name. It says nothing about caching (force_refresh exists in the schema), authorization needs, or rate limits, which are the remaining traits an agent would want for a long enumerable list.

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?

Short, front-loaded, and every sentence carries information; the purpose and read-only status come first. The final sentence on item shape is partly redundant with the existing output schema, which slightly dilutes the economy.

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?

Purpose, read-only nature, and the name-to-ID resolution workflow are all covered, and an output schema exists so return values need not be spelled out. For a zero-required-parameter lookup tool this is nearly complete; only cross-caching/permission behavior is unaddressed.

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% and each of the four parameters is documented in-schema, including the useful hint that the school list is long and paginate='all' enables name search. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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+resource ('List schools for education records') plus the scope ('education records'), which cleanly separates it from list_board_schools and the other list_* enumeration tools. The agent knows exactly what this returns without opening the 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?

Explicitly ties the tool to its downstream use: 'Resolves school names to IDs (school_id) for add_education', which tells the agent when this call is needed. It stops short of naming an exclusion or alternative (e.g. list_board_schools, list_degrees), so it is clear context rather than 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