viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

erc8004__score_agent

Computes a decay-weighted trust score in [0,1] and tier from on-chain ERC-8004 feedback, giving more weight to recent behavior and defaulting to neutral 0.5 when no feedback exists.

Instructions

[erc8004 — MCP-native bridge to ERC-8004 on-chain identity] Decay-weighted trust score in [0,1] + tier over the agent's imported ERC-8004 feedback — recent behavior outweighs old; no feedback scores a neutral 0.5 prior (no blind trust, no unfair zero).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain_id`	No
`token_id`	No
`bridge_did`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.12Jul 28, 2026
Removedv0.1.11Jul 18, 2026
Changed11 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / bridge_did / title
```
Removed value: -"Bridge Did"
```
- removedInput schema / properties / chain_id / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / chain_id / default
```
Removed value: -null
```
- removedInput schema / properties / chain_id / title
```
Removed value: -"Chain Id"
```
- addedInput schema / properties / chain_id / type
```
Added value: +"integer"
```
- removedInput schema / properties / token_id / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / token_id / default
```
Removed value: -null
```
- removedInput schema / properties / token_id / title
```
Removed value: -"Token Id"
```
- addedInput schema / properties / token_id / type
```
Added value: +"integer"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"score_agentArguments"
```
Changed11 schema fields changedJul 13, 2026
- addedInput schema / properties / bridge_did / title
```
Added value: +"Bridge Did"
```
- addedInput schema / properties / chain_id / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / chain_id / default
```
Added value: +null
```
- addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```
- removedInput schema / properties / chain_id / type
```
Removed value: -"integer"
```
- addedInput schema / properties / token_id / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / token_id / default
```
Added value: +null
```
- addedInput schema / properties / token_id / title
```
Added value: +"Token Id"
```
- removedInput schema / properties / token_id / type
```
Removed value: -"integer"
```
- removedInput schema / required
```
Removed value: -[]
```
- addedInput schema / title
```
Added value: +"score_agentArguments"
```
Changed11 schema fields changedJul 13, 2026
- removedInput schema / properties / bridge_did / title
```
Removed value: -"Bridge Did"
```
- removedInput schema / properties / chain_id / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / chain_id / default
```
Removed value: -null
```
- removedInput schema / properties / chain_id / title
```
Removed value: -"Chain Id"
```
- addedInput schema / properties / chain_id / type
```
Added value: +"integer"
```
- removedInput schema / properties / token_id / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / token_id / default
```
Removed value: -null
```
- removedInput schema / properties / token_id / title
```
Removed value: -"Token Id"
```
- addedInput schema / properties / token_id / type
```
Added value: +"integer"
```
- addedInput schema / required
```
Added value: +[]
```
- removedInput schema / title
```
Removed value: -"score_agentArguments"
```
First observedJul 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions decay weighting and neutral default score, but fails to disclose whether the tool is read-only, destructive, or requires specific permissions. It does say 'bridge to on-chain identity', implying a read operation, but not explicitly.

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?

Two sentences with no fluff. Front-loaded with key identity information. However, it could include brief parameter hints without losing conciseness.

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

Completeness3/5

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

Explains output (score and tier) and edge case (no feedback → 0.5). But 'tier' is not defined, and no output schema exists. For a simple scoring tool, it is mostly adequate but could be more precise.

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

Parameters1/5

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

Schema has 3 parameters (chain_id, token_id, bridge_did) with 0% description coverage. The tool description does not explain these parameters at all, leaving their purpose and format completely unspecified.

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?

Description clearly states it computes a decay-weighted trust score in [0,1] plus tier based on ERC-8004 feedback. It specifies 'bridge to ERC-8004 on-chain identity', distinguishing it from generic trust scoring tools like trust__score_agent.

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?

Implied usage context: it operates on 'imported ERC-8004 feedback'. However, it does not explicitly state when to use this tool versus alternatives (e.g., trust__score_agent), nor does it mention prerequisites or use cases.

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

Deploy Server

erc8004__score_agent

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools