Skip to main content
Glama

Photos On This Day

photos_on_this_day
Read-onlyIdempotent

Retrieves photos and videos taken on a calendar day in earlier years, newest year first, to help you revisit memories and see which years contain media.

Instructions

Photos and videos taken on this calendar day in earlier years ("on this day"), newest year first: {date, years: [{year, items, more}], years_checked}. more: that day holds more than shown (photos_list with from_date=to_date=that day lists them all). One Google request per year, so keep years modest.

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_on_this_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day to look back from (default: today)
yearsNoHow many earlier years to look at
per_yearNoAt most this many items per year

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior. The description adds meaningful context beyond that: one Google request per year, a warning to keep years modest, and the semantics of the `more` flag including the exact follow-up call to list all items.

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 front-loaded with the core behavior, then tacks on the return shape, `more` handling, and cost note. Every sentence earns its place and the structure is efficient for a specialized retrieval tool.

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?

With annotations covering safety, a full output schema, and 100% parameter coverage, the description completes the picture: it explains the return shape, the `more` overflow path, and the per-year request cost. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds cost-aware guidance for `years` ('One Google request per year, so keep years modest'), which tells the agent something the schema's maximum: 20 does not. `per_year` and `date` are left to the schema, so it is not a 5.

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: photos and videos taken on this calendar day in earlier years, newest year first. It also names photos_list with from_date=to_date as the alternative when the day holds more than shown, so an agent can distinguish it from siblings without opening schemas.

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?

The 'on this day' purpose makes the use case clear, and the description explicitly routes the agent to photos_list when `more` is true. It does not compare against photos_search or photos_list for general listing, and gives no explicit when-not guidance, so it falls short of a 5.

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