Skip to main content
Glama

The Cultural Signal

Art-world salary data

salary_data
Read-only

Aggregated art-world salary ranges by role and currency from published job postings (CC BY 4.0; buckets with 5+ postings only).

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": "salary_data"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely useful context beyond them: the data is aggregated rather than individual, comes from published postings, is CC BY 4.0 licensed, and small samples are suppressed (5+ postings only). The suppression rule matters because it tells the agent some roles will be absent. It does not describe the shape of the returned ranges or which currencies exist.

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?

A single dense sentence with no filler, front-loading the resource and then layering scoping, provenance, licensing, and the suppression rule. Every clause carries information an agent would otherwise have to guess.

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 zero-parameter, read-only reference tool with no output schema, the description gives what an agent needs: what the data is, where it comes from, and its coverage limits. The only real gap is that the return structure (fields, range format, currency set) is not hinted at, which matters slightly more because no output schema exists.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to elaborate. Baseline 4 applies; the description's mention of role and currency dimensions is a bonus hint at the result structure rather than parameter documentation.

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 (aggregated art-world salary ranges) plus the two dimensions it is broken down by (role, currency) and the source (published job postings). An agent can tell this is a reference dataset rather than the postings themselves (art_jobs) or editorial content (latest_stories). It stops short of explicitly naming a sibling it is not.

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?

Usage is only implied: an agent infers it should call this when it needs salary benchmarks by role or currency. There is no explicit when-to-use condition, no statement of when not to use it, and no pointer to art_jobs for individual postings. Minimal but adequate guidance for a zero-parameter lookup.

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