Skip to main content
Glama

slickpic_guide

Learn how to review client proofing, organize galleries, and prepare photo delivery in SlickPic, including key screens and the sign-in link. Call this first.

Instructions

How to work in SlickPic (review client proofing, organize galleries and prepare photo delivery): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in SlickPic, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the nature of the output (screens and a sign-in link), which implies a read-only informational tool, and it signals a prerequisite role via "Call this first." It does not say whether the content is static documentation or task-dependent, nor how large the response is or whether the task argument changes what is returned.

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?

One tight sentence with the core instruction ("Call this first") trailing the scope clause. The parenthetical example list is dense but earns its place by scoping the guide's coverage. No redundant restatement of the name.

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 low-complexity, zero-required-parameter orientation tool with no output schema, the description covers what it is, roughly what it returns, and when to call it. The main remaining gap is whether the response is fixed reference text or shaped by the task argument, which an agent might want to know before calling.

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

Parameters3/5

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

There is a single optional parameter with 100% schema description coverage, so the schema already explains it as free-text task intent. The description adds no semantics about how task influences the guide content or whether omitting it yields default orientation material. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific resource: guidance on working in SlickPic, with parenthetical scope (client proofing, gallery organization, photo delivery) plus what the guide covers (screens, sign-in link). This is clearly an informational/orientation tool, distinct in kind from the action-oriented siblings (click, open, type, read). It stops short of explicitly contrasting itself with those siblings, which keeps it from 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?

"Call this first" is an explicit, unambiguous sequencing instruction that tells the agent to invoke this before the browser-action siblings. There is no statement of when not to call it (e.g. once oriented, or for a task with no SlickPic relevance), so it falls short of full when/when-not guidance.

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