Skip to main content
Glama

picsum_get

Read-onlyIdempotent

Retrieve details for a specific Lorem Picsum photo by ID to identify the image and support browser automation or AI agent workflows.

Instructions

Get info about a specific Lorem Picsum photo by ID.

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": {
      "id": "<id>"
    },
    "name": "picsum_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPhoto ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds nothing beyond that — no indication of what 'info' contains (author, dimensions, URLs), whether missing IDs error, or what the call costs.

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?

A single front-loaded sentence with no padding. It is appropriately short for a one-parameter lookup, though brevity here comes at the cost of any added substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place an agent could learn what 'info' is returned, and it gives none of that. For a trivia-lookup tool this is a real gap, not a stylistic one.

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?

Only one parameter, and the schema already documents it at 100% coverage ("Photo ID"). The description's 'by ID' restates the schema rather than adding format, validation, or source-of-ID guidance.

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?

Specific verb (get) plus resource (Lorem Picsum photo) plus identifier (by ID) makes the operation unambiguous. It implicitly contrasts with picsum_list and picsum_random_url but never names them, so it falls short of full sibling differentiation.

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?

The 'by ID' phrasing implies you must already have a photo ID, which hints at when to use it over the list/random tools, but no alternative is named and no conditions are spelled out.

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