Skip to main content
Glama
Sign In
segment-mcp

segment-mcp

by pedromfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_destination

Retrieve a single Segment destination by ID to inspect its full settings and configuration, such as regional endpoint and app ID.

Instructions

Get a single Segment destination by id, including its full settings/config (e.g. the Intercom regional endpoint and app id).

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": {
      "destinationId": "<destinationId>"
    },
    "name": "get_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationIdYesThe Segment destination id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 burden. It discloses that the response includes full settings/config (with an example), which is useful, but it does not explicitly state that the operation is read-only or describe any permissions, rate limits, or error behavior.

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 wasted words. It immediately states the action, the resource, and the key return detail.

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 read tool with one parameter and no output schema, the description adequately covers what is returned (full settings/config) and how to identify the destination. Minor gaps like error behavior are acceptable given the low complexity.

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%, and the single parameter 'destinationId' is already documented in the schema. The description adds no syntax or format details beyond 'by id', so the baseline of 3 applies.

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?

States a specific verb and resource ('Get a single Segment destination by id') and distinguishes itself from the sibling list_destinations by specifying 'single'. The mention of full settings/config further clarifies the scope of the destination object returned.

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 implied by 'Get a single ... by id', which suggests calling it when you need one destination's full configuration. However, there is no explicit guidance on when to prefer this over list_destinations, get_source, or other siblings, nor any stated exclusions.

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