Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_trust_score

Adjust an agent's trust score to influence its memory ranking in collective searches. Only admin can apply a delta between -100 and +100.

Instructions

调整 Agent 信任分（-100 到 +100 的增量）。信任分影响 collective 记忆搜索排序，高信任 Agent 的记忆排名靠前。仅 admin 可调用。

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": {
      "agent_id": "<agent_id>",
      "delta": "<delta>"
    },
    "name": "set_trust_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
deltaYes信任分增量（正数加分，负数扣分）
agent_idYes目标 Agent ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.6

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that the operation is an increment (delta), the valid range, the impact on memory ranking, and the authorization requirement. Without annotations, the description adequately covers behavioral traits.

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 concise sentences packed with essential information: range, effect, and access control. No superfluous 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?

Explains purpose, effect, and access. Lacks explicit mention of return value or error handling, but for a simple adjustment tool with well-defined parameters, the description is largely complete.

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 already describes both parameters ('agent_id' and 'delta') with clear explanations. The tool description adds no new semantic detail beyond the schema, so baseline of 3 is appropriate.

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 adjusts an agent's trust score with a specific range (-100 to +100) and explains the effect on memory search ranking. It distinguishes from the sibling 'recalculate_trust_scores' by implying manual adjustment.

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?

Explicitly states 'only admin can call', providing a clear access restriction. While it does not explicitly mention when not to use it, the admin constraint offers sufficient guidance for appropriate use.

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