Skip to main content
Glama

update_contract_setting

Destructive

Updates a contract's consume_user_resource_percent (user pay ratio) using the contract creator's wallet to adjust how resource costs are shared.

Instructions

Update a contract's consume_user_resource_percent (user pay ratio). Requires the contract creator's wallet.

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": {
      "contractAddress": "<contractAddress>",
      "consumeUserResourcePercent": "<consumeUserResourcePercent>"
    },
    "name": "update_contract_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
contractAddressYesThe contract address
consumeUserResourcePercentYesNew consume_user_resource_percent value (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is covered. The description adds the meaningful constraint that the caller must hold the contract creator's wallet, which is auth context not present in the schema or annotations. It stops short of saying whether the change is immediately irreversible on-chain or what the response looks like.

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?

Two tight sentences with no filler; the operation and the key prerequisite are both front-loaded. Nothing could be removed without losing information.

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 single-field mutation with full schema coverage and annotations carrying the destructive/idempotency profile, the description covers purpose, target field, and the auth prerequisite. Only secondary details, such as on-chain finality or cost implications, are absent, and no output schema exists to require explanation.

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%, so all three parameters are documented structurally, and that sets the baseline at 3. The description does add domain meaning by glossing consume_user_resource_percent as 'user pay ratio', a small but real value-add beyond the schema's near-tautological field text.

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?

States a specific verb (Update), resource (contract's consume_user_resource_percent), and even glosses the field as '(user pay ratio)'. This clearly distinguishes it from sibling update_* tools that touch accounts, energy limits, or witnesses, though it never names an alternative explicitly.

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?

Provides one important prerequisite ('Requires the contract creator's wallet'), which tells the agent a condition for success. However, there is no explicit when-to-use vs. when-not guidance and no routing to sibling tools like get_contract or update_energy_limit.

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

Deploy Server

Other Tools