Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Update Segment Tool

update-segment-tool
DestructiveIdempotent

Overwrites the given fields; previous values are not kept. Rename an existing segment. The name is optional, so a call that omits it leaves the segment unchanged. Names are unique per project, case-insensitive, so renaming to a duplicate (in any casing) returns an error.

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": "update-segment-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe segment label (max 64 characters). Names are unique per project, case-insensitive, so "Direct Competitors" and "direct competitors" collide.
segment_idYesThe numeric id of the segment to update.

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?

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered, but the description adds genuinely useful detail: previous values are not retained, and renaming to a case-insensitive duplicate returns an error. It does not mention permissions or what the response contains, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the destructive consequence front-loaded, which is the right ordering for an agent scanning for risk. The collision rule is stated twice (once in the description, once in the schema), a minor redundancy.

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 two-parameter, single-required-field rename tool with no output schema, the description covers the mutation semantics, optionality behavior, and the one error condition an agent is likely to hit. Missing only auth/permission expectations and return-value shape, neither of which is required here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a non-obvious behavioral fact: because 'name' is the only mutable field, omitting it leaves the segment entirely unchanged. The uniqueness/case-insensitivity rule is repeated from the schema rather than extended, so the added value is real but modest.

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 names a specific verb and resource ('Rename an existing segment') and clarifies the overwrite semantics up front, so an agent can identify the operation immediately. It stops short of differentiating itself from siblings such as create-segment-tool or delete-segment-tool by name, which is the only missing piece for a 5.

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 rather than stated: the definition makes clear this acts only on an existing segment and that omitting the name is a no-op, which steers an agent away from pointless calls. There is no explicit routing advice, such as using create-segment-tool for new segments or delete-segment-tool for removal.

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