Muralists Directory

Search muralists

search_muralists

Read-only

Search a curated directory of muralists and street artists in Europe. Filter by country, city/region and style (e.g. abstract, figurative, lettering, photorealistic, geometric). Returns matching artists with portfolio highlights and profile URLs. Use this when someone wants to find, hire, or commission a mural artist.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of artists to return (1-10).
`query`	No	Free text over name, tagline, bio, city and styles.
`style`	No	Style label, e.g. abstract, figurative, lettering, photorealistic, geometric.
`region`	No	City, province or region the artist is based in, e.g. 'Rotterdam', 'Noord-Holland', 'Berlin'. Matches city or region.
`country`	No	Country, as an ISO 3166-1 alpha-2 code ('DE') or its Dutch name ('Duitsland'). By default matches where the artist is BASED.
`include_travel`	No	With `country`: also return artists who will WORK there without being based there (they named the country, said 'all of Europe', or have a current or upcoming travel period there).

Output Schema

Name	Required	Description	Default
`results`	Yes
`total_matches`	Yes	How many artists matched before the limit was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Country, as an ISO 3166-1 alpha-2 code ('DE') or its Dutch name ('Duitsland'). By default matches where the artist is BASED.",
+  "type": "string"
+}

addedInput schema / properties / include_travel

Added value: +{
+  "description": "With `country`: also return artists who will WORK there without being based there (they named the country, said 'all of Europe', or have a current or upcoming travel period there).",
+  "type": "boolean"
+}

changedInput schema / properties / region / description

Previous value: -"Dutch city, province or region, e.g. 'Rotterdam', 'Noord-Holland'. Matches city or region."New value: +"City, province or region the artist is based in, e.g. 'Rotterdam', 'Noord-Holland', 'Berlin'. Matches city or region."

changedOutput schema / properties / results / items / properties / city / description

Previous value: -"Dutch city the artist is based in."New value: +"City the artist is based in."

addedOutput schema / properties / results / items / properties / country

Added value: +{
+  "description": "ISO 3166-1 alpha-2 country the artist is based in.",
+  "type": "string"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "id",
-  "name",
-  "city",
-  "styles",
-  "summary",
-  "notable_works",
-  "profile_url",
-  "accepts_commissions"
-]New value: +[
+  "id",
+  "name",
+  "city",
+  "country",
+  "styles",
+  "summary",
+  "notable_works",
+  "profile_url",
+  "accepts_commissions"
+]

First observedSep 1, 2026

TDQS

A3.8/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 safety and closed-world behavior are covered. The description adds the curated/Europe scope and return contents, but does not disclose auth needs, rate limits, pagination, or other behavioral limits, making 3 appropriate.

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?

Four sentences, front-loaded with purpose and scope, followed by filters, return contents, and usage trigger. Every sentence contributes and there is no filler.

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?

Given the annotations and output schema, the description is largely complete: it covers purpose, filters, returns, and a clear use case. It omits sibling routing and the include_travel/limit nuances, though the schema handles those details, leaving only a minor gap.

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%, so all six parameters are already documented in the schema. The description restates the main filters and style examples but adds no syntax, matching rules, or edge-case meaning beyond the schema; baseline 3 applies.

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 verb and resource: "Search a curated directory of muralists and street artists in Europe," with clear geographic and domain scope. It does not explicitly distinguish itself from siblings like get_muralist_profile or generic search, so it falls 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 Guidelines4/5

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

Provides a clear usage trigger: "Use this when someone wants to find, hire, or commission a mural artist." It does not state when not to use it or name alternatives, so it is strong but not exhaustive.

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

All Muralists Directory 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?