Skip to main content
Glama

Kubeez

plan

Read-onlyIdempotent

Scope: none (any authenticated key). Read-only planner. Input: free-text user intent (REQUIRED — e.g. 'a hero image for my coffee brand', 'animate my product photo', 'add a cigar to the monkey in this video', 'separate vocals from this song'). Optional flags — PASS THESE when relevant or the planner will mis-route: has_local_files=true if the user attached image / audio reference media; has_video_reference=true if the user attached a VIDEO and wants it modified (video-to-video editing — e.g. "add X to this clip", "restyle this video", "make the subject do Y"). When video_reference is true the planner routes to a video-ref model (Gemini Omni Video HD video-ref) instead of text/image-to-video, which is the correct choice for editing an existing clip. Output: a structured plan with recommended_model, estimated_credits, estimated_seconds, requires_upload, suggested_aspect_ratio, workflow_steps[], and skills_to_fetch[]. Use this as the FIRST call of a session when the user describes a goal but hasn't picked a model. It collapses get_models → get_balance → estimate → human-guidance into a single round-trip and tells you exactly which skills to read before generating. After the plan, fetch each item in skills_to_fetch (via get_skill or resources/read kubeez://skills/<name>), then follow workflow_steps in order. This tool does NOT charge credits and does NOT call any model — it's pure deterministic routing on top of the model catalog + skill index. If the intent is ambiguous, the plan returns clarifying_questions[] instead of a model recommendation; ask the user those, then call plan again.

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": {
      "intent": "<intent>"
    },
    "name": "plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYes
target_aspectNo
has_local_filesNo
has_video_referenceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the tool charges no credits, calls no model, is deterministic routing over the catalog, and may return clarifying questions instead of a plan. It also warns about mis-routing when flags are omitted, which is genuinely non-obvious behavior. Minor gap: it doesn't say how large or slow the returned plan is, but that is low value given the output schema.

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?

Front-loaded with scope, then inputs, then output, then usage — a sensible order, with the mis-routing warning placed next to the flags it applies to. It loses a point because the enumerated output fields restate what the output schema already provides, and the parenthetical examples of has_video_reference are somewhat repetitive.

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

Completeness4/5

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

For a routing tool with a real output schema, the description covers the full call lifecycle: when to call, what to pass, what comes back, and what to do next. The only substantive hole is the undocumented `target_aspect` parameter, which matters because aspect choice affects routing/model selection.

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?

Schema coverage is 0% and the schema carries only titles, so the description must carry the load — and it does for three of four parameters, giving worked intent examples and precise routing semantics for has_local_files and has_video_reference. `target_aspect` is never mentioned, leaving one parameter undocumented in both schema and description.

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?

States a specific role ('Read-only planner') and a concrete output contract: a structured plan with recommended_model, estimated_credits, workflow_steps[], skills_to_fetch[]. It explicitly distinguishes itself from the siblings it collapses (get_models → get_balance → estimate), so an agent can tell it apart from `estimate` or `pick_model` without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('FIRST call of a session when the user describes a goal but hasn't picked a model'), an explicit fallback path for ambiguity (clarifying_questions[] → ask user → call plan again), and a follow-up sequence (fetch skills_to_fetch, then follow workflow_steps). It also tells the agent when to set the optional flags and what goes wrong if it doesn't.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources