Skip to main content
Glama
Sign In
photos-mcp

photos-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Photos Status

photos_status
Read-onlyIdempotent

Check session health, snapshot age, remaining daily budgets, cache size, and last error for the photo library assistant without calling Google.

Instructions

Session account and generation, snapshot age, breaker, daily budgets left, cache size and the last error. Never calls Google.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: it lists exactly what state is surfaced (breaker, daily budgets left, cache size) and that the call incurs no upstream Google request, which matters for rate-limit reasoning.

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?

Two short sentences, no filler, with the returned state front-loaded and the no-upstream-call constraint placed last. The telegraphic noun list ('breaker', 'generation') is compact at the cost of a little readability.

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?

An output schema exists and there are no parameters, so the description need not document return shapes or inputs; its job is only to say what the snapshot covers, which it does. Some jargon (breaker, generation, snapshot age) is left unexplained for an agent unfamiliar with the service.

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 parameter semantics carry no burden; the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

Enumerates the specific diagnostic fields it reports (session account/generation, snapshot age, breaker, budgets, cache size, last error), which clearly marks it as a status/health readout rather than a media operation, distinguishing it from the album/search/upload siblings. No explicit verb, but the resource is unambiguous.

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?

'Never calls Google' implies it is the cheap, quota-free check an agent should run before attempting live calls, but the description never states that condition explicitly nor names an alternative. Usage is inferable rather than stated.

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