Skip to main content
Glama
Sign In
sketchy-mcp

sketchy-mcp

by ddkbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Choose photo-labeling model

choose_model

Select and download the local vision model for locate during one-time setup; change it later if needed.

Instructions

Show the user a picker to choose and download the local vision model used by locate (one-time setup, can be changed later).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full transparency burden. It does disclose the important behavioral traits that this is an interactive user-facing picker, that it triggers a model download, and that it is a one-time/reconfigurable operation. It omits the download size, storage location, behavior on cancel, and whether it blocks, which are material for a network-and-disk-touching setup tool.

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?

A single sentence that front-loads the action ('show the user a picker'), then the resource, then the consumer, with a parenthetical for lifecycle context. Every clause carries information and none of it is redundant.

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?

This is a zero-parameter, annotation-free tool with no output schema, so the description only needs to explain the interaction and its consequences. It does that, covering the picker, the download, and reconfigurability, though it leaves the return value and failure behavior implicit.

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 input schema declares zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed beyond the user's choice in the picker.

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 gives a concrete verb and resource: 'show the user a picker to choose and download the local vision model'. It also names the consumer, 'the local vision model used by locate', which tells an agent why the model exists. It stops short of differentiating from the sibling tools download_model and model_status, whose scopes overlap with 'choose and download'.

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?

'one-time setup, can be changed later' clearly frames the situation in which this tool applies and reassures the agent that the choice is not permanent. There is no explicit exclusion, such as a statement of when to use download_model or model_status instead, so the routing guidance is contextual rather than definitive.

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