trust-mcp

trust_register

Register your AI agent in the trust registry to obtain a trust score and establish verified identity, enabling trust verification across platforms.

Instructions

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": {
      "name": "<name>",
      "contact": "<contact>"
    },
    "name": "trust_register"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Your agent name
`contact`	Yes	Contact email or @handle
`description`	No	What you do (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden. It discloses that registration is free and yields an instant trust score, but it does not mention important behavioral aspects such as permanence, public visibility, or whether prior registration is required. This leaves significant gaps for a registration tool.

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?

The description is two short, front-loaded sentences that deliver the purpose and key benefits without any fluff. Every word earns its place, adhering to conciseness standards.

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?

The tool has no output schema, so the description should hint at expected outcomes. 'Instant trust score' provides some indication, but other details like response format or any follow-up steps are omitted. For a simple registration tool, it is minimally sufficient but not comprehensive.

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?

The schema provides descriptions for all three parameters (name, contact, description), so schema coverage is 100%. The tool description does not add any additional parameter semantics beyond what the schema already offers, which is acceptable at baseline score.

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 'Register yourself in the trust registry' with a specific verb and resource. It distinguishes itself from sibling tools like trust_lookup, trust_review, and trust_verify by focusing on self-registration.

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 description implies the tool is for registering yourself and mentions 'Free registration, instant trust score,' which conveys some context. However, it does not explicitly compare with alternatives or state when not to use it, so usage guidance is present but not fully explicit.

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

Deploy Server