Skip to main content
Glama
Sign In
sketchy-mcp

sketchy-mcp

by ddkbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get viewer data

get_view

Returns the data behind a Sketchy view, enabling the viewer to render or inspect the diagram content.

Instructions

Returns the data behind a Sketchy view. Used by the viewer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "view": "<view>"
    },
    "name": "get_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description bears the full disclosure burden. 'Returns' weakly implies a read, but nothing is said about permissions, whether a view must already exist, failure behavior, or payload size — a thin disclosure for a tool with zero annotation coverage.

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?

Two short sentences with the core action front-loaded and no filler. The brevity is efficient, though it borders on under-specification rather than tightness.

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

Completeness2/5

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

With no output schema, the description should characterize what comes back, and 'the data' does not. Combined with an unexplained parameter and no annotations, an agent lacks enough to invoke this confidently beyond a blind string argument.

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

Parameters2/5

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

Schema coverage is 0% and the single 'view' parameter is an undocumented bare string. The description adds no format guidance — ID vs. name vs. path — so the agent must guess what value to supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Returns' and the object 'the data behind a Sketchy view' give a recognizable purpose, but 'data' is vague — an agent cannot tell whether this yields geometry, metadata, or a rendered payload. Sibling names (sketch, search_parts, find_image) are clearly different resources, so differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'Used by the viewer' hints at a consumer context but never says when an agent should call this versus going through the viewer surface or another sibling. No prerequisites, exclusions, or alternative routing are given.

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