Skip to main content
Glama
Sign In
LLM Router MCP

LLM Router MCP

by Devatva24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

plan_workflow

Design a feature's high-level workflow and architecture using Gemini, producing a clear blueprint that guides implementation.

Instructions

Always uses Gemini to plan a high-level workflow or architecture for a feature.

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": {
      "prompt": "<prompt>"
    },
    "name": "plan_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYes
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only mentions 'Always uses Gemini'. It does not explain what happens to the prompt, whether context is updated, return format, or any side effects, which is insufficient for a planning tool.

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 a single concise sentence. However, 'Always uses Gemini' is a minor filler that does not aid purpose clarity, preventing a perfect score.

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?

Despite having only 2 parameters and no output schema, the description omits critical context: what the plan looks like, how session_id affects behavior, and how this tool relates to siblings like generate_code or implement_feature. The agent is left without enough guidance for correct use.

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% for both parameters. The description vaguely implies the 'prompt' describes a feature, but gives no detail on expected content or format, and 'session_id' is entirely unexplained. The description fails to compensate for the lack of schema documentation.

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 clearly states the verb 'plan' and the resource 'high-level workflow or architecture for a feature', making the core purpose evident. It does not explicitly distinguish from sibling tools like generate_code or implement_feature, but the planning focus is implicitly different.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, timing, or when not to use it, leaving the agent to infer from the tool name and siblings.

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