Skip to main content
Glama

Pipeline Next Actions Tool

pipeline-next-actions
Read-only

Lists persisted pipeline attention items for the authenticated business without changing, dismissing, or executing them. Use to inspect the next pipeline actions in the connected business. Returns filters, actions, summary, scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pipeline-next-actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of actions to return.
priorityNoOptional priority filter.
due_beforeNoOnly actions due on or before this local date.
action_typeNoOptional exact action type.
action_stateNoPipeline state; defaults to open.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
actionsYesBounded actions records returned by this tool.
filtersYesFilters metadata; empty collections retain their existing JSON array representation.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "actions": {
      +      "description": "Bounded actions records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "filters": {
      +      "description": "Filters metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "filters",
      +    "actions",
      +    "summary",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is supplied structurally; the description's "without changing, dismissing, or executing them" restates it with useful specificity. Beyond that it adds little — no note on pagination, persistence semantics, or default state (the open default lives only in the schema).

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?

Three short sentences with the read-only guarantee front-loaded, so an agent gets the key constraint immediately. The final sentence, "Returns filters, actions, summary, scope," is wasted effort given an output schema exists.

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

Completeness4/5

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

For a read-only, fully documented five-parameter list tool with an output schema and rich annotations, the description covers purpose, scope, and mutation safety well. The one real gap is disambiguation from the similar pipeline-recommendations tool, which the description never addresses.

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 100%, with every parameter documented and two enums enumerated, so the schema does the heavy lifting. The description adds no syntax, format, or interaction detail (e.g., how due_before interacts with action_state) beyond what is already structured.

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?

Description gives a specific verb and resource: "Lists persisted pipeline attention items for the authenticated business", plus an explicit negative scope ("without changing, dismissing, or executing them"). It does not differentiate itself from the adjacent sibling pipeline-recommendations, so an agent must still guess which of the two 'pipeline' tools to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to inspect the next pipeline actions in the connected business" states a general context but gives no when-not conditions, no prerequisites, and no routing guidance relative to pipeline-recommendations. Usage is implied rather than decided.

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