Skip to main content
Glama

Find similar scenes

find_similar
Read-onlyIdempotent

Scenes that look like a chosen one, from precomputed visual similarity, filtered to the published catalogue. Each of the first 12 results comes with a signed image.

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

Input Schema

NameRequiredDescriptionDefault
idNo
limitNo
cursorNo
imagesNoReturn a signed image for each of the first 12 results (true by default)
scene_idNo
exclude_brandNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts: similarity is precomputed and results are restricted to the published catalogue, and only the first 12 results carry signed images. It omits pagination behaviour via cursor and does not say which parameter actually supplies the seed scene.

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?

Two tight sentences with the scope constraint front-loaded and no filler. Minor awkwardness in 'a chosen one', which is less precise than naming the seed scene identifier would be.

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?

An output schema exists so return values need no explanation, but for a six-parameter tool with no required parameters the definition leaves the caller unable to determine how to specify the source scene or how to page. That gap is material to correct invocation, not cosmetic.

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 only 17%, so the description must carry the load, and it does not. It never distinguishes the two near-identical identifier parameters (id and scene_id, same pattern and length), nor explains exclude_brand's boolean-or-brand-slug union or the limit ceiling of 50, leaving the most consequential ambiguity unresolved.

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 resource (scenes), the relationship (visually similar to a chosen one), and the source (precomputed visual similarity restricted to the published catalogue). It stops short of naming any sibling it differs from, e.g. search_scenes, pattern_search or search_by_moment, so an agent must infer the boundary itself.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives, despite several nearby similarity/search tools. The phrase 'from precomputed visual similarity' hints at the use case but gives no selection criteria against its siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources