Skip to main content
Glama

Pipeline Recommendations Tool

pipeline-recommendations
Read-only

Lists persisted pipeline recommendations for the authenticated business without generating, editing, approving, rejecting, or executing them. Use to review pipeline recommendations in the connected business. Returns filters, recommendations, summary, scope, draft_history.

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-recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum recommendations to return.
statusNoRecommendation state; defaults to pending.
action_typeNoOptional exact pipeline recommendation action type.
recommendation_idNoOptional exact recommendation ID.
include_draft_historyNoWhen true, recommendation_id is required and bounded draft edit history is returned.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "draft_history": {
      +      "description": "Draft history metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "filters": {
      +      "description": "Filters metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "recommendations": {
      +      "description": "Bounded recommendations records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "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",
      +    "recommendations",
      +    "summary",
      +    "scope",
      +    "draft_history"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/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 covered. The description still adds real value by stressing that nothing is generated, edited, approved, rejected, or executed, and by noting the data is persisted rather than computed live. It does not discuss pagination or rate limits, which keeps it just short of a 5.

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?

The opening sentence is front-loaded with the verb, resource, and the non-mutation guarantee, and the second sentence routes usage. The trailing return-key list ("Returns filters, recommendations, summary, scope, draft_history") is partly redundant given the tool has an output schema, which is the only wasted space.

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?

With full schema coverage, an output schema, and read-only annotations, the description only needs to establish scope and confirm the tool is a pure read. It does both. The minor gap is that the relationship to pipeline-next-actions is never stated, which matters in a catalog of 32 siblings.

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%, so every parameter (limit, status, action_type, recommendation_id, include_draft_history) is already documented with defaults, bounds, and an enum. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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 gives a specific verb and resource ("Lists persisted pipeline recommendations") plus a scope ("for the authenticated business") and a negative enumeration that rules out generation, editing, approval, rejection, and execution. It is unambiguous what the tool does, though it never names the sibling it differs from (e.g. pipeline-next-actions), so the differentiation is inferential rather than explicit.

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 review pipeline recommendations in the connected business" restates the purpose rather than giving a decision rule. The exclusion clause implies when not to use it (anything that mutates or generates recommendations), but no alternative tool or prerequisite is named, so guidance is only implied.

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