Skip to main content
Glama
Sign In
@vitrion/zentria-mcp

@vitrion/zentria-mcp

Official
by vitrionbv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-default-pipeline

Read-only

Retrieve the team's default sales pipeline to identify the correct sales stages for managing CRM data.

Instructions

Fetch the team default sales pipeline (GET /api/public/sales/pipeline). Scope: sales:read.

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": "get-default-pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds the REST method/path and the sales:read scope, which is useful context beyond the annotation. However, it does not disclose what 'default' resolves to, possible empty/error behavior, or response shape; there is no contradiction.

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 sentence contains the action, resource, endpoint, and scope with no filler. Everything is front-loaded and every word earns its place.

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 fetch, the description is nearly complete: it states what is fetched, the endpoint, and the required scope. The only gaps are explicit differentiation from sibling pipeline tools and a note about return shape, both minor at this complexity level.

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 has zero parameters, so the input schema fully covers semantics and there is nothing for the description to add. Baseline for zero parameters is 4, and the description includes endpoint/scope context that supports correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Fetch') and resource ('team default sales pipeline'), and includes the exact endpoint and auth scope. This distinguishes it from siblings like get-pipeline and list-pipelines without requiring the agent to open schemas.

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?

No explicit guidance is given for when to use this tool versus list-pipelines or get-pipeline, and no alternatives are named. The phrase 'team default' implies the intended use case, but the description leaves the choice to inference.

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

Deploy Server

Other Tools