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

@vitrion/zentria-mcp

Official
by vitrionbv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-stl-flow

Read-only

Fetch a Speed to Lead flow by ID to view its configuration and details in Zentria CRM. Retrieve specific flow data for analysis or verification.

Instructions

Fetch a Speed to Lead flow (GET /api/public/stl/flows/{id}). Scope: stl:read.

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": {
      "id": "<id>"
    },
    "name": "get-stl-flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFlow id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, and the description adds the specific HTTP GET method and required stl:read scope without contradicting the annotations. It does not mention error responses or return shape, but for a simple read-only fetch the disclosed endpoint and scope are meaningful behavioral context.

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 entire description is one compact sentence that front-loads the action and resource, then appends the endpoint and scope. There is no filler or redundancy; every element 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 single-parameter, read-only GET operation with no output schema, the description is largely complete: it gives the endpoint, scope, and resource. The only minor gap is that it does not describe the expected response shape or not-found behavior, but the simple fetch semantics make this a marginal omission.

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%: the id parameter is fully documented with type, bounds, and required status. The description adds no parameter-level detail, but the baseline 3 applies because the schema already carries the full semantic burden.

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 names a specific verb ('Fetch'), a specific resource ('Speed to Lead flow'), and the exact GET endpoint with an {id} parameter. This clearly distinguishes it from list-stl-flows, update-stl-flow, and delete-stl-flow, and leaves no ambiguity about what the tool does.

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?

The description implies this tool retrieves a single known flow by id, but it does not explicitly state when to prefer it over list-stl-flows or when to use alternatives like update-stl-flow/delete-stl-flow. The endpoint and scope provide context, but no direct usage guidance is given.

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