Skip to main content
Glama
Sign In
elk-mcp

elk-mcp

by cocrates
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_algorithms

Lists available elkjs layout algorithms with metadata, such as layered, mrtree, and force, to select one before computing graph layouts.

Instructions

List registered elkjs layout algorithms with metadata. Use before layout_graph to pick algorithm (layered, mrtree, force, ...).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, but description implies a safe read-only operation. Provides examples of algorithms (layered, mrtree, force) to set expectations. No need for additional behavioral details.

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 sentences, zero waste. Front-loaded with purpose and actionable context (use before layout_graph). Every sentence earns its place.

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

Completeness5/5

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

Given zero parameters, no output schema, and simple tool nature, the description is fully complete. It explains what the tool lists, why to use it, and gives examples.

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?

No parameters; schema coverage is 100% (trivially). Description adds context (elkjs layout algorithms) beyond the empty schema, earning a baseline of 4.

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

Purpose5/5

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

Clear verb+resource: 'List registered elkjs layout algorithms with metadata'. Distinguishes from sibling 'layout_graph' by specifying its preparatory role.

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?

Explicitly says 'Use before layout_graph to pick algorithm', providing clear usage context. Does not mention when not to use, but for a listing tool this is sufficient.

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