Skip to main content
Glama

pic_time_guide

Get step-by-step guidance on Pic-Time screens, sign-in links, galleries, visitors, favorites, store orders, and clients. Call this first to learn how to work in Pic-Time.

Instructions

How to work in Pic-Time (galleries, visitors, favorites, store orders and clients): 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": "pic_time_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Pic-Time, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It implies a read-only informational tool by describing content (screens, sign-in link), but never states that it performs no actions itself or whether it returns static text, a navigation result, or live state — a meaningful gap for a tool whose whole purpose is orienting an agent.

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

Conciseness5/5

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

Two short sentences with zero waste: the scope enumeration sits in a parenthetical and the critical instruction, 'Call this first,' is placed at the end for emphasis. Nothing is redundant or padded.

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

Completeness3/5

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

For a single-optional-parameter guidance tool with no output schema, the definition covers scope and call order, but leaves unclear what the caller actually receives (documentation text, screen list, a link) and whether it can be re-called mid-task. Adequate but not complete.

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 only one optional parameter and the schema documents it at 100% coverage ('What you want done in Pic-Time, in your words'), so the baseline is 3. The description adds nothing about how the task string shapes the response (e.g., whether guidance is filtered by the stated intent).

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 the resource (Pic-Time's galleries, visitors, favorites, store orders, clients) and the artifact returned (screens and the sign-in link), which clearly separates it from the sibling action tools like pic_time_click or pic_time_open. It is slightly fuzzy on the verb — 'How to work in' implies reference/guidance rather than a concrete operation — but an agent can still tell this is the orientation/knowledge tool.

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 ordering rule that tells the agent when to reach for this tool relative to all siblings. It stops short of stating when not to use it or what to call instead for a specific action, but for a guidance tool the first-call rule is the essential guidance.

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