Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_bond_health

Checks live SolvScore reputation-bond health, flags slash anomalies, and returns bond status so you can verify agent credit trust without webhooks.

Instructions

[FREE] Live SolvScore reputation-bond market health, derived from real slash events in the live agent credit economy (invention #4037). Returns bond_health (true when the 24h slash volume stays within 2.5x of the trailing 10-day baseline AND the AgentPay ops bonds are intact), slash_anomaly, badges outstanding, slash events in the last 24h, and the per-agent ops bond status. This is the same signal that rides every x402-agent-pay.com/facilitator/verify success response - a live trust status with no webhook service needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bond_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it states the operation is free, discloses the exact threshold logic (24h slash volume within 2.5x of a trailing 10-day baseline AND AgentPay ops bonds intact), and lists the returned signals. Gaps remain on freshness/caching cadence and rate limits, but the core behavioral contract is disclosed rather than left to inference.

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?

The one-paragraph description is front-loaded with the '[FREE]' marker and the core purpose, then moves to return contents. Some framing is promotional ('invention #4037', 'live agent credit economy') and could be trimmed, but it does not obscure the operational content.

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?

There is no output schema and no annotations, yet the description compensates by enumerating every returned field and the boolean's evaluation rule, which is what an agent needs to interpret the response. Combined with the trivial zero-parameter surface, the definition is close to complete for its 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?

The tool takes zero parameters and the empty schema accurately reflects that; the description consistently implies a no-argument status read, so nothing is undocumented. Per the baseline for zero-parameter tools, this is a 4.

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?

The description pairs a specific verb and resource — 'Live SolvScore reputation-bond market health' — and enumerates exactly what the payload contains (bond_health, slash_anomaly, badges, 24h slash events, per-agent ops bond status). This differentiates it reasonably from near siblings like get_credit_market_stats and get_solvency_ratio, 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?

Usage is only implied: the '[FREE]' tag and the note that this is the same signal carried on every facilitator/verify success response suggest a cheap pre-check or monitoring call, and 'no webhook service needed' hints at polling. There is no explicit statement of when to call this versus get_agent_trust_pulse, get_credit_market_stats, or check_facilitator_liveness, and no exclusions.

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