Skip to main content
Glama

list_pipeline_assignees

Read-onlyIdempotent

List the active team members who can be assigned enquiries in the approved business.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered without the description. The description adds two real behavioral facts beyond that: results are filtered to "active" team members only, and scope is bounded by the "approved business" tenancy. It does not state what fields each assignee entry contains or whether the list is ever empty, which is where the remaining gap lies.

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

Conciseness5/5

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

A single front-loaded sentence with no filler, no restatement of the tool name, and every clause carrying distinct information (active-only, assignable-to-enquiries, business-scoped). Nothing could be removed without losing meaning.

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 zero-parameter, read-only enumeration tool with full annotation coverage, the description plus annotations are nearly sufficient. The one missing piece is the shape of the returned items (names? ids? email addresses?), which matters because the result presumably feeds an assignee field elsewhere and there is no output schema.

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

Parameters4/5

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

The tool takes no input parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs, and additionalProperties is false, consistent with a parameterless call.

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?

"List the active team members who can be assigned enquiries" gives a specific verb (List), a precise resource (active team members assignable to enquiries), and a scope qualifier ("in the approved business"). An agent can immediately tell this is the assignee-enumeration tool, distinct from the enquiry-listing siblings. It stops short of a 5 only because it doesn't explicitly contrast itself with the closest alternatives.

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?

Usage is only implied: the phrase "who can be assigned enquiries" hints the result is meant to feed an enquiry-assignment step, but there is no explicit when-to-use statement or reference to a sibling such as update_pipeline_enquiry. For a zero-parameter read-only lookup the risk of misuse is low, so a middle score is fair rather than punitive.

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