Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Get Segment Tool

get-segment-tool
Read-onlyIdempotent

Fetch a single segment by its numeric id. Optionally pass include to load the parent project chain.

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": {
      "segment_id": "<segment_id>"
    },
    "name": "get-segment-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `project`, `project.organization`.
segment_idYesThe numeric id of the segment to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds that include loads the parent project chain, which is useful behavioral context, but it does not describe error behavior or the returned segment shape.

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 two focused sentences with the core action front-loaded and no redundant wording. Every sentence contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only, two-parameter fetch tool with fully described schema and explicit annotations, the description provides sufficient context to select and invoke it correctly. No output schema exists, but the expected behavior is clear enough for this tool 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 coverage is 100%, and the schema already documents both segment_id and include, including whitelisted values. The description adds slight semantic meaning by calling include the 'parent project chain', but the schema remains the primary source of parameter details.

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 and resource ('Fetch a single segment') and scopes it by 'numeric id' plus optional include behavior. This clearly distinguishes it from sibling segment tools such as create, update, delete, attach, and detach.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage condition clear: retrieve one segment by id, with an optional include for parent project chain. It does not explicitly name alternatives or when-not-to-use cases, but for a single-record fetch tool the context is sufficiently clear.

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

All Pineprompt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources