PatternStack

signals.evaluate

Evaluate package actions for dependency management by analyzing compatibility, security, and framework context to provide data-driven recommendations.

Instructions

Get reward signal for add/remove/upgrade/replace actions

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": {
      "action": "<action>",
      "package": "<package>",
      "currentStack": "<currentStack>"
    },
    "name": "signals.evaluate"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action type
`package`	Yes	Package to evaluate
`targetPackage`	No	Target package (for replace action)
`targetVersion`	No	Target version (for upgrade action)
`currentStack`	Yes	Current packages
`framework`	No	Framework context
`ecosystem`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jan 29, 2026

TDQS

C2.9/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 burden of behavioral disclosure. It states the tool 'Get reward signal', which implies a read-only, non-destructive operation, but doesn't elaborate on what a 'reward signal' entails, potential side effects, rate limits, or authentication needs. For a tool with 7 parameters and no annotations, this is a significant gap in transparency.

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 description is a single, efficient sentence: 'Get reward signal for add/remove/upgrade/replace actions'. It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity, making it highly concise and well-structured.

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?

Given the tool has 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what a 'reward signal' is, how it's used, or the expected return values, leaving significant gaps for an AI agent to understand the tool's full context and behavior.

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?

The schema description coverage is high at 86%, so the schema already documents most parameters well. The description adds minimal value beyond the schema by hinting at the action types ('add/remove/upgrade/replace'), but it doesn't provide additional context like parameter interactions or usage examples. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Get reward signal for add/remove/upgrade/replace actions'. It specifies the verb ('Get reward signal') and the resource/scope ('add/remove/upgrade/replace actions'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'architecture.evaluate' or 'dependency.safe-upgrade', which might also evaluate actions, so it doesn't reach the highest clarity level.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, and with multiple sibling tools like 'dependency.safe-upgrade' or 'stack.recommend' that might overlap in functionality, the agent lacks explicit direction on tool selection.

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

Deploy Server