holiday-photo-plus
Server Details
Show holiday photos from Vercel Blob inline in Claude chats.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly defined.
The single tool name follows a clear verb_noun pattern (get_photo), which is consistent by default.
A single tool can be acceptable for a very narrow purpose, but typical photo library operations would benefit from at least a few more tools (e.g., list, upload). The tool count is borderline.
The server only provides retrieval; it lacks obvious operations like listing available photos, uploading, or deleting, which are necessary for a complete photo library interface.
Available Tools
1 toolget_photoAInspect
Fetch a photo from the Holiday Photo Plus library and display it inline in the chat. name is the filename of the photo as it lives in the repo's public/holidayphotos/ folder (e.g. 'Photo1.png'). A substring also matches. Omit name to get a random photo.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Photo pathname, filename, or substring. Omit for a random photo. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool fetches and displays images inline, implying a read operation without destructive effects. It also specifies the source folder and substring matching behavior. With no annotations provided, this is adequate transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two short, front-loaded sentences. The first states the core purpose, and the second clarifies the parameter. No unnecessary information, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description covers parameter behavior and display effect. It could mention error handling or permissions, but overall it is sufficiently complete for the agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of the parameter, but the description adds an explicit example ('Photo1.png') and clarifies substring matching, which goes beyond the schema's description. This adds practical value for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Fetch a photo from the Holiday Photo Plus library' and specifies display behavior. The verb 'fetch' and resource 'photo' are specific, and the tool is easily distinguished from potential siblings by its unique functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides guidance on omitting the 'name' parameter for a random photo and explains substring matching. However, it does not include explicit when-not-to-use or alternative tool comparisons, though no siblings are listed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!