Skip to main content
Glama
Sign In
SuperDev

SuperDev

by Xsxdot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Suggest service runtime

suggest_service_runtime
Read-only

Generate a draft runtime configuration for a language service from the project root and current directory, then validate the result before finalizing.

Instructions

Suggest schema-shaped runtime config for a language service from project_root and cwd. Use the result as a draft, then validate it.

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": {
      "language": "<language>",
      "project_root": "<project_root>"
    },
    "name": "suggest_service_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
languageYes
project_rootYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, which the description does not contradict. The description adds that the result is a draft to be validated, implying a non-authoritative output. However, it doesn't disclose any other behavioral traits like return format or handling of invalid inputs.

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?

The description is two sentences long, front-loads the core purpose, and includes a practical instruction. No wasted words.

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?

Given no output schema and minimal annotations, the description provides the essential purpose and a hint at usage, but it doesn't explain the output structure or address all parameters. It is adequate but not rich, especially considering the dense sibling toolset.

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 description coverage is 0%, so the description must compensate. It mentions project_root and cwd, giving them some context, but the required 'language' parameter is omitted. This leaves a notable gap for a required input.

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 tool's function: 'Suggest schema-shaped runtime config for a language service from project_root and cwd.' It uses a specific verb ('suggest') and resource ('runtime config'), and implicitly distinguishes it from siblings like validate_service_runtime and describe_language_runtime_schema.

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?

It provides usage context by advising to 'Use the result as a draft, then validate it,' which implies a workflow and points toward validation as a next step. It doesn't explicitly name the validation tool but gives clear guidance on when to use the suggestion.

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