Skip to main content
Glama
Sign In
durable-mcp

durable-mcp

by cshah26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_pjm_wh

Retrieve PJM Western Hub day-ahead and real-time LMP prices and load data for a target date, with optional historical data up to 90 days.

Instructions

Get PJM Western Hub DA/RT LMP prices and load data. Use this when asked about PJM Western Hub prices, PJM WH, Eastern power prices, or PJM load.

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": {
      "target_date": "<target_date>"
    },
    "name": "get_pjm_wh"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_dateYesTarget market date in YYYY-MM-DD format
historical_daysNoNumber of historical days to include (default 7, max 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears full burden. It does not disclose read-only nature, idempotency, rate limits, auth requirements, data freshness, or any side effects. This is a significant gap for a 'get' operation that should be safe.

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?

Two concise sentences: first on purpose, second on usage. No extraneous information, front-loaded, and each sentence serves a clear function.

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?

With no output schema, the description gives a reasonable sense of what is returned (prices and load). Combined with fully described parameters, it is adequate for simple data retrieval. However, it lacks details on response structure or pagination if any.

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 coverage is 100%, so the schema already documents both parameters well. The description adds context about the returned data (prices and load) but does not elaborate further on parameter format or usage beyond the schema.

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 it retrieves PJM Western Hub DA/RT LMP prices and load data, with specific location and data types. It distinguishes well from sibling tools that handle constraints, flows, generation, etc.

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?

The description explicitly lists use cases ('PJM Western Hub prices, PJM WH, Eastern power prices, or PJM load'), but does not mention when not to use or reference sibling alternatives directly. However, the given contexts are clear for an agent.

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