Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

Get CRM Segment

crm_segment_get
Read-only

Returns one CRM segment definition: segment_id, handle, name, description, conditions, matched_count, and timestamps. Takes app_id and segment_id (uuid or handle from crm_segments_list).

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": {
      "app_id": "<app_id>",
      "segment_id": "<segment_id>"
    },
    "name": "crm_segment_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app uuid returned by `apps_list`.
segment_idYesThe segment uuid or handle returned by `crm_segments_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value by enumerating the returned fields (conditions, matched_count, timestamps) since there is no output schema. It omits error behavior, e.g. what happens with an unknown handle.

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?

Two sentences, tightly written: return payload first, inputs second, with placeholders that match the schema names. No filler, nothing redundant, and the most important information leads.

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 with annotations covering safety and no output schema, listing the returned fields plus the id-source hint is close to everything needed. The main gap is the optional organization_id resolution behavior, which neither the description nor a usage note explains beyond the schema text.

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%, so app_id, segment_id (uuid or handle), and organization_id are all documented in the schema already. The description merely restates the segment_id uuid-or-handle duality and says nothing about the optional organization_id override, so it adds no meaning beyond structured data. Baseline 3 applies.

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?

The description opens with a specific verb and resource ('Returns one CRM segment definition') and immediately enumerates the returned fields, which distinguishes a single-record fetch from the sibling list tool. It does not name crm_segments_list as the alternative operation, only as a source of handles, so it stops short of full sibling differentiation.

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: an agent can infer this is the single-record read after a list call, since the description notes segment_id may be a 'handle from crm_segments_list'. There is no explicit statement of when to use this versus crm_segments_list, nor any prerequisite or not-found caveat.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources