Skip to main content
Glama

Plan workload

plan_workload

$1 workload routing plan from declared costs and representative evaluation counts.

Up to 20 profiles and 50 task groups. Inspect the public service schema and a free unpaid quote first. Does not execute tasks or establish actual savings.

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": {
      "profiles": "<profiles>",
      "tasks": "<tasks>"
    },
    "name": "plan_workload"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYesUp to 50 task groups with representative evaluation counts.
profilesYesUp to 20 execution profiles with their declared costs.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / profiles / description
      Added value: +"Up to 20 execution profiles with their declared costs."
    • addedInput schema / properties / tasks / description
      Added value: +"Up to 50 task groups with representative evaluation counts."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the description's job is lighter. It nonetheless adds real context: the $1 cost, the pre-call prerequisites, and the explicit disclaimer that no tasks are executed and no savings are proven. That is more than the annotations convey.

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 the deliverable and cost, followed by limits and preconditions; three sentences with no filler. The limits sentence largely duplicates the input schema, which is the only small inefficiency.

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?

An output schema exists, so return values need not be explained. Given a two-parameter planning tool with full schema coverage and safety annotations, the description supplies what is missing: cost, prerequisites, and the non-execution caveat.

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 description coverage is 100%, so both parameters are already documented, and the 20-profile / 50-task-group caps are repeated from the schema rather than added. The description does reinforce that costs are 'declared' and counts are 'representative', but this is marginal beyond-schema value — the baseline 3 applies.

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?

States a specific verb and artifact: building a $1 workload routing plan from declared costs and representative evaluation counts. The scope is clear and concrete, though it does not explicitly contrast with the sibling describe_agent, so an agent must infer the boundary.

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?

Gives an explicit prerequisite sequence: inspect the public service schema and a free unpaid quote first before committing to a paid plan. It also sets a negative boundary ('does not execute tasks or establish actual savings'), but it names no alternative tool for the case where a plan is not what the caller needs.

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.