Skip to main content
Glama

list_pipeline_enquiries

Read-onlyIdempotent

List website enquiries with their pipeline stage, assignment and revision. Filter by stage, search text or assignee.

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": "list_pipeline_enquiries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
stageNo
searchNo
assigneeNo

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 readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing what each record carries (stage, assignment, revision), but it is silent on pagination behavior despite a 'page' parameter, and on result volume or default sorting.

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 with the resource and returned fields front-loaded, then the filtering surface. No filler, though the second sentence is essentially a parameter roster rather than added guidance.

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?

There is no output schema, but the description summarizes the returned record shape and the filtering options, and annotations are rich enough to convey the safety profile. The gaps — pagination and differentiation from 'list_enquiries' — are real but modest for a read-only list tool with all-optional parameters.

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 must carry the load; it names three of four parameters (stage, search, assignee) but omits 'page' entirely and adds no meaning beyond the parameter names — e.g. what fields the search text is matched against, or that stage 'all' is a passthrough. Partial compensation only.

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?

States a specific verb and resource ('List website enquiries') and names the returned fields (pipeline stage, assignment, revision), which distinguishes it from a generic enquiry list. However, it never explicitly contrasts itself with the sibling 'list_enquiries', leaving the agent to infer the difference from the word 'pipeline'.

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?

The second sentence enumerates filter dimensions (stage, search text, assignee) but says nothing about when this tool is preferable to 'list_enquiries' or 'list_pipeline_assignees', nor any prerequisites or exclusions. Filter capability is not the same as usage guidance.

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