Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_get_schedule_alert_config

Fetch read-only alert and execution configuration for a project schedule using project name and schedule ID without changing or running workflows.

Instructions

Read safe original alert/execution fields; never writes or runs a workflow.

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": {
      "project_name": "<project_name>",
      "schedule_id": "<schedule_id>"
    },
    "name": "ds_get_schedule_alert_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedule_idYes
project_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does make one valuable disclosure: the tool never writes and never runs a workflow, which reassures the agent it is safe. It says nothing about required permissions, what 'original' versus current fields means, or what the response contains, leaving substantial behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short clause with no filler, and the safety statement is front-loaded. However, the brevity crosses into under-specification rather than efficiency given the 0% schema coverage.

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-required-parameter getter with no annotations, no output schema, and no parameter documentation, the description is too thin. It does not say what fields are returned or how they are shaped, leaving the agent unable to predict the result of the call.

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 must compensate and it adds nothing: neither project_name nor schedule_id is explained (expected format, whether schedule_id is globally unique or scoped to the project). The reader can infer intent from the names but cannot confirm scoping semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a read action over 'original alert/execution fields', which gestures at the resource, but it never explicitly says it retrieves a schedule's alert configuration; the agent must lean on the tool name. No sibling is named or distinguished, even though ds_update_schedule_alerts and ds_list_schedules appear in the catalog.

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?

There is no when-to-use guidance, no prerequisites (e.g. needing a schedule to already exist), and no mention of alternatives such as ds_list_schedules for discovery or ds_update_schedule_alerts for modification. The only implicit cue is the read-only framing.

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