Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

start_system_design

Start a system design interview session by choosing a case ID and difficulty level.

Instructions

Start a system design interview session for a specific case.

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": {
      "case_id": "<case_id>"
    },
    "name": "start_system_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYesSystem design case ID from list_interview_cases
difficultyNoDifficulty levelmid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose what happens after starting (e.g., whether questions are provided, session recorded), leaving significant behavioral gaps.

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?

Single sentence, 12 words, no waste. Front-loaded with essential information.

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?

For a session-start tool with no annotations or output schema, the description is too minimal. It omits what the agent should expect after starting, hindering complete understanding.

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?

Schema coverage is 100%, so baseline 3. The description adds no extra meaning; parameters are already well-defined in schema.

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?

The description clearly states the action (start), the specific resource (system design interview session), and the condition (for a specific case). It distinguishes from siblings like 'start_interview_session' and 'list_interview_cases'.

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?

No guidelines on when to use this tool versus alternatives (e.g., 'start_interview_session'). No mention of prerequisites such as listing cases first.

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