Skip to main content
Glama

The Cultural Signal

Open art-world jobs

art_jobs
Read-only

Open jobs at museums, galleries and auction houses. Optional filters: role (e.g. curatorial, registrar, sales, marketing) and city slug (e.g. new-york, london, paris, hong-kong).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "art_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
roleNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing about sort order, pagination, default result count, or what a listing contains, which are the behaviors an agent would still want for a listings endpoint.

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?

Two lean sentences, with the resource statement front-loaded before the filter guidance. No filler, though the filter sentence could note that both filters are combinable.

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 simple read-only, zero-required-parameter listing tool with no output schema, the definition covers what the tool returns at a high level and how to narrow it. The remaining gap is result-size/pagination behavior tied to the undocumented limit parameter.

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?

Schema description coverage is 0%, so the description must carry the semantics, and it does for two of three parameters: it explains role with concrete domain examples (curatorial, registrar, sales, marketing) and clarifies that city is a slug with formats like new-york and hong-kong, which is exactly what the opaque pattern regex would not convey. The limit parameter is never mentioned, leaving its default of 20 and cap of 50 undisclosed.

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?

States a specific resource (open jobs) and narrows the scope to museums, galleries and auction houses, which separates it from siblings like fair_calendar and salary_data. It does not explicitly name a sibling it is 'not', so it stops short of 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 Guidelines3/5

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

Framing the filters as 'optional' implies the tool can be called bare to browse all open jobs, which is useful. There is no explicit when-to-use or when-not-to-use guidance relative to search_stories or fair_calendar, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources