Skip to main content
Glama

get_brokerage

Read-onlyIdempotent

Query a Super Representative's brokerage ratio to see the dividend percentage they keep and how much is distributed to voters. Provide the SR witness address, with optional network selection.

Instructions

Query the brokerage ratio (dividend percentage) of a Super Representative. The brokerage value is the percentage that the SR keeps; the rest is distributed 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": {
      "witnessAddress": "<witnessAddress>"
    },
    "name": "get_brokerage"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
witnessAddressYesThe SR witness address

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

A4/5.0
Behavior4/5

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

The annotations already declare this tool to be read-only, idempotent, non-destructive, and to have an open-world hint. The description therefore only needs to add domain context, which it does: it explains that the returned percentage is what the SR keeps, while the rest goes to voters. It does not describe behavior on an invalid address, how the network defaulting works, or the return type, so it is good rather than exhaustive.

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?

Only two sentences are used, and both earn their place: the first states the what and the who, and the second disambiguates the metric. The definition is front-loaded with the action and has zero 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 simple two-parameter read tool with full schema coverage, complete annotations, and no output schema, the definition covers purpose and domain semantics. The remaining gap is minor: it does not state the return type or range, such as a percentage value, which would help the agent interpret results.

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%, and the schema documents both witnessAddress ('The SR witness address') and network ('Defaults to mainnet'). The description adds no parameter-level detail beyond that and does not explain whether witnessAddress accepts a public key, an address, or an alternate form. Baseline 3 applies when the schema carries the full burden.

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?

The description uses a specific verb and resource: 'Query the brokerage ratio (dividend percentage) of a Super Representative.' It maps directly to the sibling read tool get_brokerage and is clearly distinct from update_brokerage. It also defines what 'brokerage' means, so the agent knows the value's semantics before calling.

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 guidance is only implicit: it says 'query,' which signals a read, but it never says when to use this tool versus siblings such as update_brokerage or get_account. It also never says when not to use it. The domain explanation of brokerage implies the context, but no explicit trigger is given.

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