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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get statistics

get_statistics
Read-only

Retrieve read-only library statistics to view total photo count, video count, and storage usage without listing individual assets.

Instructions

Get library statistics. Use this for a quick overview of library size without listing individual assets. Read-only.

Returns: JSON with total photo count, video count, and storage usage in bytes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 destructiveHint=false, so the 'Read-only' sentence restates structured data rather than adding to it. The remaining content enumerates return fields, which duplicates the declared output schema. Nothing extra about cost, caching, or freshness of the counts is disclosed.

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?

Short and front-loaded: purpose first, then usage, then read-only, then returns. The 'Read-only' line and the Returns paragraph both restate structured fields (annotations, output schema), so a small amount of the text does not earn its place.

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 tool with full annotation coverage and an output schema, the description covers purpose, when to prefer it, and a return summary. It is essentially complete; only sibling differentiation versus search_statistics 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?

The tool takes zero parameters, so there is no parameter meaning to convey; baseline for an empty schema would be 4. However, the description spends a sentence describing return values already covered by the output schema instead of adding semantic value.

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 ('Get library statistics') and clarifies scope with 'quick overview of library size without listing individual assets.' This distinguishes it from listing tools in spirit, though it never names the closest sibling, search_statistics, so an agent must still infer the difference.

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 clear usage condition: use it when a size overview is wanted rather than enumerating individual assets. There is no explicit when-not guidance and no mention of the search_statistics sibling, which is the one plausible source of confusion in this tool set.

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