Skip to main content
Glama
Sign In
sketchy-mcp

sketchy-mcp

by ddkbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Model status

model_status

Reports the photo-labeling model's state for the model picker, helping users see which model is active or available.

Instructions

Report the state of the photo-labeling model. Used by the model picker.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

B3.3/5.0
Behavior2/5

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

No annotations or output schema are supplied, so the description carries the full behavioral burden. It says 'Report' but does not confirm read-only behavior, explain what state values are returned, or describe what the report contains.

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?

The description is two short sentences and front-loads the core purpose. The second sentence adds useful context, though it is somewhat vague about how the model picker uses it.

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 zero-parameter status tool, the description is sufficient to know how to invoke it. But with no output schema, it should clarify what 'state' includes, such as ready, downloading, or unavailable, so an agent knows how to interpret the result.

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 tool takes zero parameters, so parameter semantics are not applicable. The empty schema is consistent with the description, and the baseline for zero-parameter tools is 4.

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 a specific verb and resource: 'Report the state of the photo-labeling model.' It also ties the tool to the model picker, making its role clear. It does not explicitly distinguish itself from siblings like choose_model or download_model, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Used by the model picker' gives implied context for when this tool matters. However, it does not say when to use this versus choose_model or download_model, nor does it state any prerequisites or exclusions.

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