Skip to main content
Glama

update_pipeline_enquiry

Update an enquiry stage and assignment using its current pipeline revision. Pass null to clear the assignment.

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": {
      "id": "<id>",
      "stage": "<stage>",
      "assignedTo": "<assignedTo>",
      "revision": "<revision>"
    },
    "name": "update_pipeline_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
stageYes
revisionYes
assignedToYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation; the description adds real value by stating that the current pipeline revision is required (optimistic concurrency) and that null clears the assignment. It does not, however, say what happens on a revision mismatch, whether stage changes are constrained by transition rules, or whether anything else is overwritten.

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

Conciseness4/5

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

Two short sentences, front-loaded with the mutation and immediately followed by the one non-obvious sentinel behavior. No filler, though the second sentence lacks a subject (what exactly is cleared) that would cost one extra word to fix.

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 4-required-param mutation with no output schema and zero schema description coverage, the essentials (required revision, null semantics) are present. Missing conflict/failure behavior and any statement of the result make it only adequate, not complete.

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 description coverage is 0%, so the description carries the full burden; it explains the meaning of revision ("current pipeline revision") and the null sentinel for assignedTo, which is genuinely useful. It says nothing about id's expected format or identifiers, the stage enum values, or revision's origin, leaving half the parameters to be guessed.

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 names a specific verb and resource ("update an enquiry stage and assignment") and adds the scoping concept of a pipeline revision. It is clear what the tool mutates, but it does not contrast itself against siblings such as update_class_session or triage_contact_enquiry, so differentiation rests on the name alone.

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 explicit when-to-use or when-not-to-use guidance, and no mention of what to do when the revision is stale. An agent must infer that this is the tool for changing stage/assignee on an existing enquiry purely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources