Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Attach Brand To Segment Tool

attach-brand-to-segment-tool
Idempotent

Attach a brand to a segment. Idempotent: attaching a brand that is already attached succeeds without change. Both the brand and the segment must belong to the same project. Membership is what makes a brand a competitor, so attaching a discovered brand starts tracking it and attaching an ignored brand revives it, clearing its ignored mark. The own brand is implicit in every segment, so attaching it changes nothing.

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": {
      "brand_id": "<brand_id>",
      "segment_id": "<segment_id>"
    },
    "name": "attach-brand-to-segment-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_idYesThe numeric id of the brand to attach.
segment_idYesThe numeric id of the segment to attach the brand to. Must belong to the same project as the brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the same-project precondition, the side effect of clearing an ignored mark, and the no-op case for the own brand. The idempotency sentence largely restates idempotentHint=true, and failure behavior (nonexistent ids, cross-project rejection) is left unspecified, keeping 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?

Four short sentences, front-loaded with the operation and then the conditions, with no filler. Minor redundancy between the idempotency sentence and the annotation prevents a perfect score.

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 mutation with rich annotations, the description covers preconditions, side effects, and no-op cases adequately. With no output schema, it leaves the return value unexplained, which is the only notable gap.

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%, with both parameters already documented as numeric ids and the same-project constraint stated in the segment_id schema. The description reinforces that constraint but adds no new semantics about the parameters themselves, so the baseline 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?

Opens with a specific verb+resource: "Attach a brand to a segment." The rest of the description elaborates the meaning of that operation rather than restating the name, so an agent can distinguish it from detach-brand-from-segment-tool without opening any schema.

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?

Gives concrete when-to-use context: attaching a discovered brand starts tracking it, attaching an ignored brand revives it, and attaching the own brand is a no-op. It does not explicitly name detach-brand-from-segment-tool as the inverse or state when not to call, so it stops short of full routing guidance.

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