Skip to main content
Glama
Sign In
immich-photo-manager

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search places

search_places
Read-only

Resolve a place name via Immich’s built-in gazetteer to fix spelling or get coordinates before geographic photo searches. Read-only; returns matching places, no assets involved.

Instructions

Look a place name up in Immich's built-in gazetteer (no assets involved). Use this to resolve a spelling or get coordinates for a place before a geographic search. Read-only.

Args:
    name: Place name to look for (e.g. 'Lisbon').

Returns: JSON with a places array of {name, admin1name, admin2name, latitude,
longitude}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' and the safety profile add nothing new. The genuinely additive claims are that the lookup hits a static built-in gazetteer with no asset involvement, but the description says nothing about what an empty or ambiguous result looks like or how many matches are returned.

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?

Front-loaded with purpose and usage, then a compact Args section and return shape; the example place name earns its place. The 'Returns:' block partly restates an output schema that already exists in structured form, so there is minor redundancy.

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?

One required parameter, annotations covering the safety profile, and an output schema present, so the description only needs purpose, usage, and parameter meaning — all supplied. Nothing an agent needs in order to call this correctly is missing.

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 0%, so the single parameter is documented only by the description's 'name: Place name to look for (e.g. 'Lisbon')' plus an example. That is helpful but leaves matching behavior unstated — whether it is prefix, fuzzy, case-sensitive, or requires exact spelling — which matters for a gazetteer lookup whose stated purpose is resolving spellings.

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?

States a specific verb and resource ('look a place name up in Immich's built-in gazetteer') and immediately scopes it with '(no assets involved)', which separates it from the asset-oriented search_* siblings like search_metadata and search_explore. An agent can tell what this does without opening the schema.

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?

Gives a concrete usage context: 'resolve a spelling or get coordinates for a place before a geographic search', which tells the agent when this tool is the right first step. It does not explicitly name the alternatives (e.g. reverse_geocode, search_cities) or state when not to use it, so it stops short of full when/when-not routing.

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

Deploy Server

Other Tools