Skip to main content
Glama
research-workflow-studio

research-workflow-studio

by BorgDiven

rws_overview_dismiss

Idempotent

Dismisses an overview suggestion from review and records the project revision and proposal reference, keeping approval human-controlled.

Instructions

Human review only. MCP cannot approve its own suggestion; use the application review screen.

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": {
      "requestId": "<requestId>",
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "proposalRef": "<proposalRef>",
      "baseRevision": "<baseRevision>"
    },
    "name": "rws_overview_dismiss"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
requestIdYes
proposalRefYes
baseRevisionYes
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • changedInput schema / properties / proposalRef / properties / type / enum
      Previous value: -[
      -  "research",
      -  "experiment",
      -  "code",
      -  "run",
      -  "artifact",
      -  "protocol",
      -  "dataset",
      -  "evaluation",
      -  "comparison",
      -  "analysis",
      -  "report",
      -  "conversation",
      -  "proposal",
      -  "usage",
      -  "spec",
      -  "amendment"
      -]New value: +[
      +  "research",
      +  "experiment",
      +  "code",
      +  "run",
      +  "artifact",
      +  "protocol",
      +  "dataset",
      +  "evaluation",
      +  "comparison",
      +  "analysis",
      +  "report",
      +  "conversation",
      +  "proposal",
      +  "usage",
      +  "spec",
      +  "amendment",
      +  "server",
      +  "repository",
      +  "environment",
      +  "operation"
      +]
  2. First observedv0.3.3

TDQS

D1.5/5.0
Behavior2/5

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

The human-review-only gating is genuine behavioral context beyond the annotations, but it is framed around 'approve' rather than dismissal, so it does not clarify what this tool mutates. Annotations already say readOnlyHint=false and destructiveHint=false, so the description should explain what state change a dismissal causes and whether it is reversible — it does neither.

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

Conciseness2/5

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

It is short, but brevity here is under-specification, not concision: both sentences spend their words on a restriction and an unrelated verb. Nothing is front-loaded about the tool's actual action.

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

Completeness1/5

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

For a mutation with five required parameters, optimistic-concurrency revisions, a nested reference object, and no output schema, the description supplies none of the context needed to invoke it correctly. An agent could not call this tool from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five required parameters with 0% schema description coverage, including a nested proposalRef with a 20-value enum, and the description says nothing about any of them. There is no hint of what expectedRevision versus baseRevision mean or why requestId is required.

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

Purpose1/5

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

The description never states what the tool does — 'dismiss' appears only in the name and is never explained. Worse, it references 'approve', which is the opposite action and the job of the sibling rws_overview_apply, making the text actively misleading about which action this tool performs.

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?

It redirects the agent to 'the application review screen' rather than guiding it on when the tool itself applies, and it never distinguishes this from rws_overview_apply or rws_amendment_dismiss. The redirect is a usable signal but comes with no condition about what to do instead (e.g., escalate to a human).

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