Skip to main content
Glama

filming-locations

by com.thefilmmap

Search filming locations by name

search_locations

Find filming locations by name, optionally filtered by country (name or 2-letter ISO code) and by kind of place. Results are ordered by fame rank, which is driven by the most widely covered production shot there rather than by the place itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesPlace name or part of one, e.g. "skellig", "petra"
countryNoCountry name or ISO code (optional)
categoryNoKind of place — key or slug: studio (Studios & sets), castle (Castles & palaces), landmark (Landmarks & buildings), street (Streets & squares), nature (Landscapes & nature), city (Towns & cities), region (Countries & regions) (optional)

TDQS

A4/5.0
Behavior4/5

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

The description discloses the ordering behavior (by fame rank) and mentions optional filtering, providing good transparency without annotations.

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 description is concise, two sentences, and directly states the purpose and key behaviors without unnecessary detail.

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?

The description covers the main functionality and ordering but does not specify the return format, though that may be implied for a search tool; overall it is sufficiently complete for typical use.

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?

The schema provides detailed descriptions for all parameters, and the tool description does not add significant extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states that it finds filming locations by name, with optional filters for country and kind of place, distinguishing it from other location-based tools.

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 usage when searching by name but does not explicitly mention alternatives or when not to use it, so it provides only implied usage guidance.

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

All filming-locations toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool answers a distinct query type: aggregate statistics, country counts, nearby places, ranked places, name searches, production-to-places, and place-to-productions. The two full-question tools are clearly explicit inverses, so an agent should rarely select the wrong one.

Naming Consistency3/5

The set mixes multiple patterns: get_/list_/search_ verb prefixes, noun-based names like top_locations and locations_near, and full question phrases like what_was_filmed_here. Each name is descriptive, but there is no single consistent verb_noun convention across the surface.

Tool Count5/5

Eight tools is well-scoped for a read-only atlas: core lookup, inverse lookup, name search, geospatial search, ranking, country aggregates, and headline statistics. No tool feels redundant or missing at the same level of detail.

Completeness5/5

The domain is covered comprehensively: production-to-places, place-to-productions, location search, nearby search, ranking, country counts, and dataset-level statistics. For a Wikidata-backed read-only atlas there are no obvious dead ends; finer-grained scene data is explicitly out of scope.

Resources