Skip to main content
Glama
Sign In
Hevo MCP Server

Hevo MCP Server

by felixjoy89hevo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_pipeline

Retrieve a pipeline's full configuration and status by its numeric ID.

Instructions

Get full configuration and status of a single pipeline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline_id": "<pipeline_id>"
    },
    "name": "get_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipeline_idYesNumeric ID of the pipeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies a read-only operation via 'Get' and discloses that the result includes both configuration and status, but it does not mention error handling, permissions, or side effects. This is minimal but not misleading.

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?

The description is a single sentence, immediately front-loaded with the verb, resource, and scope. It contains no unnecessary words and is highly efficient.

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 simple single-pipeline getter with one parameter, the description is sufficiently complete. It explains the purpose and the high-level return content ('full configuration and status'), which partially compensates for the lack of an output schema.

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?

The input schema fully documents the single parameter pipeline_id with type and description (100% coverage). The tool description adds no further parameter semantics, so the baseline score of 3 is appropriate.

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 uses a specific verb 'Get' with a clear resource 'pipeline' and scope 'single', distinguishing it from sibling tools like list_pipelines. It precisely states what the tool returns: full configuration and status.

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 context is implied by the phrase 'single pipeline' which contrasts with list_pipelines, but there is no explicit when-to-use guidance or mention of alternatives. The description suggests using it for detailed inspection of a specific pipeline without stating when not to use it.

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