Skip to main content
Glama
Sign In
Plant Simulation Research Bridge

Plant Simulation Research Bridge

by AmaneSuzuha000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

schedule_vs_reference

Compares a dispatch engine schedule against an independent reference oracle for one policy and instance, revealing correctness differences in scheduling experiments.

Instructions

Compare the dispatch engine schedule with the independent reference oracle for one policy.

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": {
      "instance": "<instance>",
      "policy": "<policy>"
    },
    "name": "schedule_vs_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYes
instanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the comparison operation but does not disclose whether the tool is read-only, whether it runs a simulation, what permissions are needed, or what side effects or errors may occur.

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 definition is a single front-loaded sentence with no unnecessary wording. It efficiently states the comparison target and scope.

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 two-parameter tool with no annotations and no output schema, the description is too thin. It omits instance semantics, operational behavior, and any indication of what the comparison produces, leaving important invocation details undocumented.

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 should compensate by explaining both parameters. It mentions 'one policy' but does not explain the required 'instance' parameter, its accepted object-or-string forms, or how the two inputs relate.

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 states a specific verb and resource: comparing the dispatch engine schedule with an independent reference oracle for one policy. It is clear what the tool does, though it does not explicitly distinguish itself from other comparison or simulation tools.

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

Usage Guidelines3/5

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

The phrase 'for one policy' implies the tool is used for single-policy schedule validation against a reference, but there is no explicit when-to-use guidance, prerequisites, or mention of when not to use it. Usage is inferable but not fully guided.

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