Skip to main content
Glama
Sign In
io.github.CE-RISE-software/dpawb

io.github.CE-RISE-software/dpawb

Official
by CE-RISE-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Prioritize Improvement Targets

prioritize

Rank improvement targets from assessment results, using optional coverage and comparison data to identify priority areas for data model enhancement.

Instructions

Rank improvement targets from one assessment_result document plus optional downstream result documents.

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": {
      "assessment": "<assessment>"
    },
    "name": "prioritize"
  }
}

Input Schema

NameRequiredDescriptionDefault
coverageNoOptional list of local coverage_result JSON document paths.
assessmentYesLocal path to one assessment_result JSON document.
comparisonNoOptional local path to one comparison_result JSON document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states a ranking operation but does not disclose whether it depends on external state, has side effects, requires permissions, or returns a specific format. Minimal transparency beyond the basic action.

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?

Single sentence, front-loaded with verb and resource, no redundant information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 3 parameters and no output schema, the description covers the main action but omits output format or behavior (e.g., does it return a ranked list?). Sibling differentiation is absent, which reduces completeness.

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% with each parameter described. The description adds conceptual context by linking 'assessment_result document' and 'downstream result documents' to the parameters, but doesn't provide additional meaning beyond the schema. Baseline 3 is appropriate.

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 action ('rank') and the resource ('improvement targets from assessment_result documents'). It distinguishes from siblings like 'coverage' and 'compare' by specifying this is a prioritization step. However, the term 'downstream result documents' is vague and doesn't explicitly map to the optional parameters coverage and comparison.

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?

No explicit guidance on when to use this tool versus alternatives like 'assess' or 'compare'. The description implies it follows assessment but doesn't provide when-not or alternative references.

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