Skip to main content
Glama

CuratorSearch

by com.curatorsearch
OverviewDiscussionsAdmin

institution_jobs

Read-onlyIdempotent

Every role one museum or gallery currently has open on the board, by institution name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
institutionYesThe institution's name, e.g. 'Philadelphia Museum of Art'. Near-misses resolve; if nothing matches, the reply says so.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPresent only when no institution of that name is on the board.
pageNoThat institution's page on curatorsearch.com.
resultsYesIts open roles, newest first.
institutionYesThe institution as the board names it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / institution / description
      Added value: +"The institution's name, e.g. 'Philadelphia Museum of Art'. Near-misses resolve; if nothing matches, the reply says so."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "institution": {
+      "description": "The institution as the board names it.",
+      "type": "string"
+    },
+    "note": {
+      "description": "Present only when no institution of that name is on the board.",
+      "type": "string"
+    },
+    "page": {
+      "description": "That institution's page on curatorsearch.com.",
+      "type": "string"
+    },
+    "results": {
+      "description": "Its open roles, newest first.",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "CuratorSearch field, one of the category values.",
+            "type": "string"
+          },
+          "deadline": {
+            "description": "Application deadline as an ISO date, or null if none is given.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "institution": {
+            "description": "Museum, gallery or organisation advertising the role.",
+            "type": "string"
+          },
+          "location": {
+            "description": "City and country as stated, or null if the posting gives none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "posted": {
+            "description": "ISO date the role was first seen on the board.",
+            "type": "string"
+          },
+          "region": {
+            "description": "CuratorSearch world region.",
+            "type": "string"
+          },
+          "salary": {
+            "description": "Pay exactly as the posting states it, or null -- most postings state none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Job title as advertised.",
+            "type": "string"
+          },
+          "url": {
+            "description": "The role's permanent page on curatorsearch.com.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "institution",
+          "category",
+          "region",
+          "posted",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "institution",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds modest context by emphasizing 'currently has open' and 'on the board,' but it doesn't reveal any deeper behavior such as freshness, ordering, or limits.

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 a single, compact sentence with no filler or repeated annotation content. The phrasing is slightly awkward ('Every role... has open') but the length and front-loading of the core idea are appropriate.

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?

For a single-parameter, read-only tool with a full input schema and an output schema, the description plus structured data covers what an agent needs to call it. It stops short of a 5 because it doesn't explicitly mention when to use this over search_jobs, which would make it fully self-contained.

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 the institution parameter already includes near-miss resolution and failure behavior. The description adds only the general notion of 'by institution name,' which provides no new meaning beyond the schema.

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 states the specific resource (open roles for one museum or gallery) and the key dimension (institution name), making its purpose clear. It lacks an explicit operative verb like 'list' or 'get', and it doesn't explicitly contrast itself with siblings like search_jobs, so it doesn't fully distinguish itself.

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?

The phrase 'by institution name' implies this tool is for a specific institution's open roles, giving a clear usage context. However, it never explicitly says when to prefer this over search_jobs, get_job, or salary_transparency, nor does it state any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CuratorSearch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources