Skip to main content
Glama

flickr_guide

Get guidance for working in Flickr: organize photos, albums, and tags; review privacy; manage comments and groups; and find screens plus the sign-in link before starting tasks.

Instructions

How to work in Flickr (organize photos, albums and tags, review privacy and manage comments and groups): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Flickr, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose that the output is informational (screens and sign-in link), implying a non-mutating orientation step, but it never states whether calling it has any side effects, requires authentication, or affects session state before the subsequent action tools.

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?

One compact sentence covering scope and return content, with no filler. The dense parenthetical list is slightly harder to scan than a plain enumeration, and the key sequencing instruction ('Call this first') sits at the end rather than being front-loaded.

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 single optional-parameter guidance tool with no output schema, the description covers what it does, what it returns, and when to invoke it relative to the workflow. The only gap is not clarifying that the task parameter is optional and what happens when it is omitted.

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 coverage is 100% and the single 'task' parameter is already described as the user's goal in their own words, so the schema does the work. The description adds no detail about how the task string shapes the guidance returned (e.g., whether it filters or just contextualizes), so baseline 3 applies.

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?

The description states the tool delivers guidance about working in Flickr and enumerates the covered areas (photos, albums, tags, privacy, comments, groups) plus what it returns (screens, sign-in link). That is enough to distinguish it from the action-oriented siblings (click, open, type, read), though it doesn't name any of them explicitly.

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?

'Call this first' gives a clear ordering rule, which is genuinely useful for an agent deciding where to start. It stops short of saying when this tool is unnecessary (e.g., if already oriented) or what to do after it, so it isn't fully explicit when/when-not guidance.

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