Skip to main content
Glama
Sign In

Sendhour

by com.sendhour
OverviewDiscussionsAdmin

Find other photos for a slide

find_slide_photos
Read-only

Other real photos for one slide of a studio slideshow made with real photos: its own search words, other words (query), or photos like one of them (related, a pin_id). Each search counts toward the workspace's daily photo searches. Show the user the image links, then put one on the slide with swap_slide_photo.

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": {
      "slideshow_id": "<slideshow_id>",
      "slide": "<slide>"
    },
    "name": "find_slide_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOther search words
slideYesSlide number, from 1
cursorNoNext page, from the last result
relatedNoA pin_id from an earlier result: photos like it
slideshow_idYesFrom get_slideshow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds material cost context the annotations cannot: each search counts against the workspace's daily photo search quota. It also adds a workflow constraint (show the user the image links before swapping), which is useful behavioral guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded and free of padding, but the opening clause 'Other real photos for one slide of a studio slideshow made with real photos' repeats 'real photos' and forces a re-read before the three modes land. Tightening that phrase would raise the score.

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 5-parameter read-only search with full schema coverage and no output schema, the description covers mode selection, quota cost, and the expected next step. It does not mention pagination beyond the cursor parameter or what a result entry contains, so an agent must infer the response shape from 'show the user the image links'.

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, but the description genuinely adds the mode-selection semantics: 'query' is alternate search words, 'related' takes a pin_id from an earlier result, and the default path uses the slide's own search words. That mapping of parameter values to distinct search behaviors is not obvious from the schema alone.

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?

States a concrete verb/resource (find other photos for one slide of a slideshow) and enumerates the three search modes, which lets an agent distinguish it from siblings like search_viral or swap_slide_photo. The phrasing 'Other real photos ... made with real photos' is repetitive and slightly obscures the core action, keeping it below a 5.

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?

Makes the three invocation modes explicit (default slide search words, custom query, or related pin_id) and names the follow-up action (swap_slide_photo) after showing links. It does not say when to prefer this over search_viral or another search tool, so no exclusion guidance.

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

All Sendhour toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources