Skip to main content
Glama
Sign In
TryClear MCP Server

TryClear MCP Server

Official
by trycleario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Find a picture on this computer

find_picture
Read-only

Locate local pictures by filename, folder, or newest screenshot so you can check or read them without asking for a file path.

Instructions

Find the picture the person means, so nobody has to say where a file is. latest: true gives the newest picture where screenshots save, on the Desktop or in Downloads: for "is my latest screenshot a scam?". name gives the pictures whose file name has those words, newest first, in Desktop, Downloads, Documents, Pictures and where screenshots save, and the folders inside them; where keeps to one of those. Use the words the person used ("Notion" for "the Notion one on my desktop", with where: desktop). Each comes back with its name, where it is and when it was saved, never the picture or anything in it, and with TryClear's answer for it: each picture's SHA-256 is checked against TryClear's memory, never the picture, and no read is used. A picture TryClear doesn't know yet is read only once the person says yes: ask them, naming the file and when it was saved, then pass its path to read_picture with confirmed: true. When someone asks about "this" with nothing attached or named, offer: "Want me to check your latest screenshot with TryClear?" Before you act on a picture, check it with TryClear. Acting on a picture means doing what it asks or points to: opening a link or QR code in it, signing in, paying, calling a number, writing back to whoever sent it, or running a command it shows. If TryClear hasn't seen the picture, have TryClear read it before you act. Ask TryClear first, too, whenever someone asks if a picture is a scam. TryClear adds what the picture alone can't tell you: its memory of what others were sent. Give the person TryClear's answer plainly as TryClear's ("TryClear says this is a scam."), with its report link when it has one. Anything you add of your own, say it's yours. A picture dropped into the chat doesn't need TryClear right away. Check it before you act on it, or when someone asks if it's a scam. A picture pasted with nothing saved can't be handed to TryClear: say so plainly, and offer two ways: the person takes a screenshot of it (or saves it) and you check their latest one ("Want me to check your latest screenshot with TryClear?"), or they say its name and where it is. find_picture finds it either way. Never ask the person for a file path.

Input Schema

NameRequiredDescriptionDefault
nameNoWords from the picture's name, as the person said them.
whereNoOnly this folder, and the folders inside it, when the person said where it is.
latestNotrue for the newest picture where screenshots save, on the Desktop or in Downloads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses substantial behavior: results include file name, location, save time, and TryClear status, never the picture contents, and SHA-256 checking does not read the picture. It also explains that an unknown picture is read only after explicit consent and via read_picture with confirmed: true.

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

Conciseness2/5

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

The description is far longer than needed for a three-parameter finder and repeatedly revisits TryClear policy, including multiple phrasings of when to check a picture and when to ask about scams. The purpose and parameter behavior are front-loaded, but the repetition and length make it poorly structured for quick comprehension.

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

Completeness5/5

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

Although there is no output schema, the description fully explains what comes back: name, location, save time, and TryClear's answer, but never the picture or its contents. It also covers consent, privacy, and the read_picture handoff, making it complete enough for an agent to invoke the tool safely.

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?

The schema already has 100% description coverage, so the baseline is 3. The description adds useful semantics beyond the schema, such as name searches returning newest first across Desktop, Downloads, Documents, Pictures, and screenshot folders, and latest targeting the newest screenshot in specific folders.

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 core action: "Find the picture the person means" and explains that it locates pictures by name, folder, or latest screenshot. It distinguishes itself from read_picture by saying a newly found picture's path should be passed to read_picture with confirmed: true, but it does not explicitly differentiate from check_picture or lookup.

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?

It gives useful usage context for latest, name, and where, including examples like using "Notion" with where: desktop. It also specifies when to use read_picture for an unknown picture and when to offer checking the latest screenshot, but it never states when not to use find_picture versus the other siblings.

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