Skip to main content
Glama

view_worker_reputation

Assess worker reputation by combining on-chain bond and observed history, with a suggested collateral amount for a job payment.

Instructions

The worker card: everything this server knows about a worker before you hire them, plus a suggested collateral amount for a job.

Combines two signals:

  1. The on chain bond (global, unfakeable): slashable stake the worker has locked behind their work. Losing an arbitrated dispute forfeits it, so a live bond is money where their mouth is.

  2. This server's own observed history (local, wash trading resistant): every contract THIS server has viewed involving the worker's key, bucketed into completions, lost disputes, abandoned jobs, and so on. It is deliberately NOT a global score: strangers cannot inflate what you personally observed.

Pass a payment amount to also get a suggested collateral to demand: high for an unknown key, lower as bond coverage and clean observed history accumulate, full collateral (or a do not hire warning) for a slashed bond or observed bad history. The suggestion is a transparent heuristic with its reasoning spelled out, not a guarantee.

Args: worker_pk: Worker pubkey hex. Defaults to your own key. payment: Optional job payment in groth. If above zero, a suggested collateral for that payment is included.

Returns a JSON worker card, or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentNo
worker_pkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses key behaviors: combines two signals, not a global score, suggests collateral via a transparent heuristic. Explains the reasoning behind the suggestion.

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?

Description is well-structured: starts with purpose, then details signals, then parameter explanation. Each sentence adds value; no fluff. Front-loaded with key information.

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

Completeness5/5

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

Given 0% schema coverage and no annotations, the description fully covers input, behavior, and output (mentions JSON worker card). It is complete enough for an agent to use correctly.

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

Parameters5/5

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

Schema coverage is 0%, but description adds full meaning: worker_pk defaults to own key, payment is optional in groth and triggers collateral suggestion. This compensates completely for lack of schema descriptions.

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 clearly states the tool shows a 'worker card' with reputation info combining on-chain bond and observed history. It distinguishes from siblings (view_contract, view_dispute) by focusing on worker reputation.

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

Usage Guidelines4/5

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

The description explains when to use it (before hiring a worker) and what it provides (suggested collateral). It doesn't explicitly state when not to use, but the context and sibling tools make it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/honeytones/idios'

If you have feedback or need assistance with the MCP directory API, please join our Discord server