Skip to main content
Glama

update_brokerage

Set an SR's brokerage ratio to define the percentage of rewards the SR keeps; the remainder goes to voters. Only an SR can call it.

Instructions

Update the SR brokerage ratio (dividend ratio). Only callable by an SR. Value is the percentage the SR keeps (0-100); the remainder goes to voters.

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": {
      "brokerage": "<brokerage>"
    },
    "name": "update_brokerage"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
brokerageYesBrokerage percentage kept by the SR (0-100). E.g. 20 means SR keeps 20%.

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.9/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, open-world mutation, so the description is not the sole source of safety context. It still adds valuable behavior: the authorization requirement (SR only) and the economic consequence of the value (remainder to voters). It omits whether the change applies immediately or only to future cycles.

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?

Three short sentences, front-loaded with the action, then the permission gate, then the value semantics. Nothing is redundant with the title and no sentence is filler.

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 setter with no output schema and annotations covering the safety profile, the description covers purpose, permission, and value meaning. What remains unsaid is timing/effect of the update and whether a response value is returned, which are minor for this complexity.

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% and the schema already documents the 0-100 range and an example for brokerage. The description nevertheless adds meaning the schema lacks — that the complement of the ratio is distributed to voters — which clarifies the parameter's real-world effect. The 'network' parameter is left entirely to 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?

States a specific verb and resource ('Update the SR brokerage ratio') plus the alias 'dividend ratio', so the agent knows exactly what changes. It does not explicitly point at the sibling get_brokerage for reading the current value, so it falls short of full sibling differentiation.

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?

'Only callable by an SR' gives a real precondition for calling, which is more than most setters offer. There is no guidance on when to change it versus alternatives, no mention of how often it may be changed, and no exclusion of the read path.

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