Skip to main content
Glama
hwc-calculator

hwc-calculator

by araujoviana

rename_price_list

Rename a saved price list by providing its URL or ID and a new name. Requires login to update the list.

Instructions

Rename a saved price list. Needs a login.

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": {
      "url_or_id": "<url_or_id>",
      "new_name": "<new_name>"
    },
    "name": "rename_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYes
url_or_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it only discloses the login requirement. For a mutation it omits whether the rename is reversible, whether the old name is preserved, and what happens on name collisions — behavioral gaps an untrusted write tool needs covered.

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?

Two short sentences with the purpose front-loaded and no filler; the login note is compact and relevant. Brevity comes at the cost of detail, but no sentence is wasted.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and zero parameter documentation, the definition is too thin — an agent cannot tell how to form url_or_id or what success/failure looks like. Only the auth prerequisite is covered.

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

Parameters2/5

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

Schema coverage is 0%, so both parameters are undocumented structurally; the description only implies a target list and a replacement name. It never explains whether url_or_id accepts a URL, an ID, or both, nor any naming constraints on new_name.

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?

"Rename a saved price list" is a specific verb plus resource, and the verb naturally distinguishes it from sibling mutations like delete_price_list and duplicate_price_list. It stops short of naming any sibling explicitly, so an agent must infer the boundary from the verb alone.

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

Usage Guidelines2/5

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

"Needs a login" is a prerequisite, not usage guidance: it says nothing about when to prefer rename_price_list over duplicate_price_list (e.g., renaming vs. copying with a new name). No when-not conditions or alternatives are offered.

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