Skip to main content
Glama

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

update_product

Idempotent

Edit a product, or pause and resume it. Only the fields you pass change.

anchor_sentences follow the add_product rules (3+, each 5-40 words, the
BUYER describing their problem); the previous set is kept so a bad edit can
be undone. active=false pauses the product: its stations stop being read and
score_signal stops accepting it until you set active=true. Products are
paused, never deleted, so their history stays.

Confirm with the operator before changing anchors or pausing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional new name.
activeNofalse pauses the product and its stations; true resumes it.
product_idYesThe product to change, from get_products.
value_propNoOptional new value proposition: the buyer's problem it solves.
descriptionNoOptional new description.
target_audienceNoOptional new audience: one buyer, described narrowly.
anchor_sentencesNoOptional replacement anchors, following the add_product rules. The previous set is kept so the edit can be undone.
buy_signal_keywordsNoOptional replacement keyword gate. Best left empty (see add_product).
competitor_keywordsNoOptional replacement list of direct substitutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / active / description
      Added value: +"false pauses the product and its stations; true resumes it."
    • addedInput schema / properties / anchor_sentences / description
      Added value: +"Optional replacement anchors, following the add_product rules. The previous set is kept so the edit can be undone."
    • addedInput schema / properties / buy_signal_keywords / description
      Added value: +"Optional replacement keyword gate. Best left empty (see add_product)."
    • addedInput schema / properties / competitor_keywords / description
      Added value: +"Optional replacement list of direct substitutes."
    • addedInput schema / properties / description / description
      Added value: +"Optional new description."
    • addedInput schema / properties / name / description
      Added value: +"Optional new name."
    • addedInput schema / properties / product_id / description
      Added value: +"The product to change, from get_products."
    • addedInput schema / properties / target_audience / description
      Added value: +"Optional new audience: one buyer, described narrowly."
    • addedInput schema / properties / value_prop / description
      Added value: +"Optional new value proposition: the buyer's problem it solves."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the previous anchor set is retained for undo, that active=false stops stations being read and halts score_signal acceptance, and that products are paused rather than deleted so history persists. These are exactly the mutation-side effects an agent needs and annotations do not convey.

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?

Front-loaded with the core action and partial-update semantics, then compact paragraphs on anchors and pausing. Every sentence carries operative information (undo, station effects, operator confirmation) with no filler.

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?

No output schema, but the description needn't explain returns. With 9 params at 100% schema coverage and no annotations describing side effects, the description supplies the missing behavioral contract (pause effects, undo, confirmations) and is complete for correct invocation.

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 real meaning on top: the anchor_sentences grammar (3+, each 5-40 words, BUYER describing their problem) and the side effects of active=false. It adds beyond the schema for the params that matter most.

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+resource ('Edit a product') plus a second mode (pause/resume) in the first sentence, and clarifies the partial-update contract ('Only the fields you pass change'). This is clearly distinguishable from add_product and update_station among the siblings.

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 an explicit precondition ('Confirm with the operator before changing anchors or pausing') and routes anchor_sentences to the add_product rules, but never explicitly states when to choose this over add_product or how to create a new product instead. Clear context, no full alternative routing.

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

All SignalPipe 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