Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_random_photo

Retrieve a random photo for your project, optionally filtered by category, using the Multi-MCPs server's aggregated API access.

Instructions

Get a random photo optionally filtered by category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo

Implementation Reference

  • The handler function for get_random_photo tool. It checks for the Unsplash access key configuration and calls the client's getRandomPhoto method with the optional category parameter extracted from the input arguments.
    async get_random_photo(args: Record<string, unknown>) {
      if (!cfg.unsplashAccessKey) throw new Error("UNSPLASH_ACCESS_KEY is not configured");
      const category = args.category ? String(args.category) : undefined;
      return client.getRandomPhoto(category);
    },
  • Tool registration object for get_random_photo within the Unsplash registration, including name, description, and input schema.
    {
      name: "get_random_photo",
      description: "Get a random photo optionally filtered by category",
      inputSchema: {
        type: "object",
        properties: { category: { type: "string" } },
      },
    },
  • Input schema for the get_random_photo tool, defining an optional 'category' property of type string.
    inputSchema: {
      type: "object",
      properties: { category: { type: "string" } },
    },
  • UnsplashClient helper method that performs the actual API request to Unsplash for a random photo, using the category as a query parameter if provided.
    getRandomPhoto(category?: string) {
      return this.request("/photos/random", { headers: this.headers(), query: category ? { query: category } : undefined });
    }
  • Invocation of registerUnsplash() in the main tool registration file, which registers the get_random_photo tool among others.
    registerUnsplash(),
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool gets a random photo with optional filtering, but doesn't disclose behavioral traits such as whether it returns metadata, image data, or URLs; rate limits; authentication needs; or what 'random' means (e.g., from a curated set or all photos).

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose and includes the key detail about optional filtering.

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?

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how randomness is determined, or provide enough context for a tool with a parameter, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions optional filtering by category but doesn't explain what categories are available, their format, or how filtering works. This adds minimal value beyond the bare schema.

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 clearly states the action ('Get') and resource ('random photo'), with optional filtering by category. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'search_photos' or 'get_photo_details'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'search_photos' or 'get_photo_details'. The description mentions optional filtering but doesn't explain when filtering is appropriate or what the tool is best suited for.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server