Skip to main content
Glama
Sign In

Pizza Developer

by com.pizzadeveloper
OverviewDiscussionsAdmin

Update idea

update_idea
Destructive

Update an idea's short name of at most 20 characters, optional detail, or impact. Nothing is generated. Only supplied fields change. Order is separate: move an idea with reorder. Archiving, declining, and restoring Ideas don't run rules. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

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": {
      "id": "<id>"
    },
    "name": "update_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the Idea.
titleNoNew short name, at most 20 characters.
impactNoProduct scope of the Idea: minor or major.
contentNoNew full detail, with lists instead of tables.
summaryNoNew summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"New full detail."New value: +"New full detail, with lists instead of tables."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds meaningful context beyond annotations: 'Nothing is generated', 'Only supplied fields change', and details about rule behavior for archiving/declining/restoring and workflow-run TypeSafe checks. It does not contradict the annotations.

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?

The purpose is front-loaded in the first sentence, and most sentences add useful behavioral context. The final sentence about TypeSafe is long and somewhat specialized, but it is relevant to understanding rule evaluation during workflow runs.

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 five-parameter mutation tool with full schema coverage and no output schema, the description gives adequate behavioral context: partial update semantics, no generation, ordering alternative, and rule-evaluation behavior. It leaves out explicit permission or reversibility details, but annotations already flag destructiveness.

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 the schema already defines all five parameters, including the impact enum and field limits. The description restates some field meanings such as short name and detail, but it omits summary and adds little parameter-specific detail beyond the schema.

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 states a specific verb and resource: update an idea's short name, optional detail, or impact. It also differentiates ordering via reorder and mentions archiving/declining/restoring behavior, though it does not explicitly contrast with create_idea or delete_idea. The purpose is clear and largely distinguishable from siblings.

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?

The description explicitly says order is separate and directs ordering changes to reorder, which is useful alternative guidance. However, it does not explicitly say when to use archive, decline, restore, or delete instead of update, so the usage guidance is implied rather than complete.

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

All Pizza Developer 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