CuratorSearch

salary_transparency

Read-onlyIdempotent

How many live museum and curatorial postings state a salary, and the median advertised figure among those that do -- the CuratorSearch Curatorial Pay Archive headline number, computed live.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	No	ISO date the figures were computed.
`note`	No	Present only when there is no salary data yet.
`citation`	No	How to cite these figures.
`liveListings`	No	Live roles on the board at the moment of the call.
`percentStatingSalary`	No	Percentage of those postings that state any pay at all.
`medianAdvertisedEurPerYear`	No	Median stated figure among those that do, annualised into euro.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "asOf": {
+      "description": "ISO date the figures were computed.",
+      "type": "string"
+    },
+    "citation": {
+      "description": "How to cite these figures.",
+      "type": "string"
+    },
+    "liveListings": {
+      "description": "Live roles on the board at the moment of the call.",
+      "type": "integer"
+    },
+    "medianAdvertisedEurPerYear": {
+      "description": "Median stated figure among those that do, annualised into euro.",
+      "type": "integer"
+    },
+    "note": {
+      "description": "Present only when there is no salary data yet.",
+      "type": "string"
+    },
+    "percentStatingSalary": {
+      "description": "Percentage of those postings that state any pay at all.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description adds that the number is 'computed live' and that the median is only among postings 'that do' state a salary, clarifying the denominator. It does not contradict annotations. This gives useful behavioral context for a zero-parameter aggregate tool, though it stops short of describing refresh rates or data source caveats.

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

Conciseness5/5

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

The entire description is a single, front-loaded sentence that states the metric, scope, and live nature without any filler. The appended brand phrase 'CuratorSearch Curatorial Pay Archive' is brief and doesn't hurt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has zero parameters, rich annotations, and an output schema, so the description does not need to detail return types. It fully captures what is calculated and the population it covers. No important calling-context information is missing.

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?

There are no parameters, and the schema coverage is trivially 100%; the baseline for zero-parameter tools is 4. The description therefore doesn't need to elaborate on parameter meanings.

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?

The description states exactly what the tool reports: the number of live museum/curatorial postings with a stated salary and the median advertised figure among those that do. It identifies the resource ('museum and curatorial postings') and distinguishes it from sibling tools like get_job or search_jobs by offering an aggregate statistic rather than job-level data. Though it lacks an explicit imperative verb, 'computed live' makes the operation clear.

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 description implies the tool is for pay-transparency aggregate statistics, but it never explicitly says when to use this tool instead of get_job, institution_jobs, or search_jobs. There are no exclusions or alternative routing cues. The context of 'headline number' is clear enough but the comparison is left to inference.

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

All CuratorSearch tools Inspect

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

Need Help?