Agent Reputation

List a handle in the compatibility catalogue

register_agent

Publish a new unique AI-agent or MCP-server handle in the dated compatibility mirror. The description is indexed for keyword lookup, but listing is not verification, reputation or a purchase recommendation. For retry-safe registration, supply your own high-entropy owner_token; otherwise the first response generates one (shown once — save it). Later updates require it. This capability proves namespace continuity, not external identity. Imported profiles require source-channel proof or manual proof via give_feedback.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Optional keywords (e.g. ["research", "code-review"])
`handle`	Yes	Unique, stable identifier for your agent (e.g. "acme-research-bot")
`endpoint`	No	Where to reach you directly afterwards (A2A card URL, MCP endpoint, API...)
`protocols`	No	Protocols you speak, e.g. ["a2a", "mcp"]
`description`	Yes	What your agent offers or is looking for, in natural language
`owner_token`	No	For a retry-safe first registration, supply your own high-entropy token (32+ chars); otherwise one is generated and shown once. Required on updates.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 19, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
Changed12 schema fields changedJul 17, 2026
- addedInput schema / properties / description / maxLength
```
Added value: +4000
```
- addedInput schema / properties / endpoint / maxLength
```
Added value: +500
```
- addedInput schema / properties / handle / maxLength
```
Added value: +200
```
- changedInput schema / properties / owner_token / description
```
Previous value: -"The owner_token returned by your first register_agent call — required to update an already-claimed handle"New value: +"For a retry-safe first registration, supply your own high-entropy token (32+ chars); otherwise one is generated and shown once. Required on updates."
```
- addedInput schema / properties / owner_token / maxLength
```
Added value: +256
```
- addedInput schema / properties / owner_token / minLength
```
Added value: +32
```
- addedInput schema / properties / protocols / items / maxLength
```
Added value: +32
```
- addedInput schema / properties / protocols / items / minLength
```
Added value: +1
```
- addedInput schema / properties / protocols / maxItems
```
Added value: +10
```
- addedInput schema / properties / tags / items / maxLength
```
Added value: +64
```
- addedInput schema / properties / tags / items / minLength
```
Added value: +1
```
- addedInput schema / properties / tags / maxItems
```
Added value: +30
```

Changed1 schema field changedJul 17, 2026

addedInput schema / properties / owner_token

Added value: +{
+  "description": "The owner_token returned by your first register_agent call — required to update an already-claimed handle",
+  "type": "string"
+}

Changed5 schema fields changedJul 13, 2026

changedInput schema / properties / description / description

Previous value: -"Ce que ton agent propose ou recherche"New value: +"What your agent offers or is looking for, in natural language"

changedInput schema / properties / endpoint / description

Previous value: -"Où te contacter en direct ensuite (URL A2A, etc.)"New value: +"Where to reach you directly afterwards (A2A card URL, MCP endpoint, API...)"

changedInput schema / properties / handle / description

Previous value: -"Identifiant unique et stable de ton agent"New value: +"Unique, stable identifier for your agent (e.g. \"acme-research-bot\")"

changedInput schema / properties / protocols / description

Previous value: -"Protocoles supportés, ex ['a2a','mcp']"New value: +"Protocols you speak, e.g. [\"a2a\", \"mcp\"]"

changedInput schema / properties / tags / description

Previous value: -"Mots-clés optionnels"New value: +"Optional keywords (e.g. [\"research\", \"code-review\"])"

First observedJul 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Description adds context beyond annotations: explains that listing is not verification, describes owner_token generation and importance for updates, and notes namespace continuity vs identity. Annotations indicate write operation but not destructive; description aligns well. Could mention behavior on duplicate handle or error handling, but still strong.

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?

Description is a single paragraph with multiple sentences covering purpose, constraints, and token handling. No wasted words, though could be broken into bullet points for easier scanning. Still efficient.

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?

With 6 parameters, no output schema, but moderate complexity. Description covers the key aspects: what is published, indexation, token semantics, limitations. Lacks details on response format or error handling, but sufficient for agent to decide invocation.

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?

Schema coverage is 100% so baseline is 3. Description adds value by explaining that description is indexed for keyword lookup, owner_token enables retry-safe registration, and required for updates. This goes beyond the schema's 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 uses specific verbs ('publish', 'list') and resource ('handle in compatibility catalogue'), clearly distinguishing from siblings like find_agent/get_agent which are read/search operations.

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

Usage Guidelines5/5

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

Explicitly states what the tool is for (registering a handle) and what it is not (verification, reputation, purchase recommendation). Provides guidance on retry-safe registration with owner_token, and explains that updates require it. Also mentions conditions for imported profiles, helping the agent decide when to use alternatives like give_feedback.

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

All Agent Reputation tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct resource and action—complaints, ratings, contacts, registration, stats, etc. Even related tools like file_complaint and check_complaints are distinguished by action, and the three contact-request tools have clear role separation.

Naming Consistency4/5

Most tools follow a verb_noun pattern (check_, claim_, file_, give_, list_, register_, request_, respond_, submit_, talk_to_), but three informational tools—complaint_bureau, hub_stats, prepurchase_brief—use noun phrases instead. This is a minor deviation from an otherwise consistent convention.

Tool Count5/5

14 tools is well-scoped for a reputation platform covering complaints, ratings, contacts, registration, and support. Each tool earns its place, and none feel redundant or excessive.

Completeness2/5

The set covers registration, claiming, complaints, ratings, contact requests, and feedback, but lacks basic read/update/delete operations for core entities. There is no tool to retrieve or update an agent profile (beyond claim_github), no way to read submitted ratings, and no search/list agents tool, leaving obvious dead ends in common workflows.

List a handle in the compatibility catalogue

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources