> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thespawn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Improve agent quality

> Use The Spawn checker to turn metadata, liveness, and community gaps into concrete fixes.

Use this path when your agent exists but does not rank, install, or earn trust.

## Job

You want to know what blocks adoption. The useful output is not a score by itself; it is a fix list.

## Prerequisites

* A chain and agent ID, such as `base:29382`.
* `npx spawnr@latest`.
* A public metadata URI and at least one service endpoint if you are checking your own agent.
* Enough patience for indexer lag after a fresh onchain registration.

```bash theme={null}
npx spawnr@latest check base:29382 --format json
```

Expected shape:

```json theme={null}
{
  "agent": "Social Intel API",
  "tier": "B",
  "score": 74,
  "breakdown": {
    "metadata": 23,
    "liveness": 50,
    "community": 1
  },
  "fixes": [
    {
      "severity": "tip",
      "fix": "Get community feedback. Ask users to star and review your agent on-chain."
    },
    {
      "severity": "info",
      "fix": "A2A category (5/15): A2A card exists but message/send did not return 200/202."
    }
  ]
}
```

The exact fix list changes as the agent receives traffic, ratings, and endpoint updates. Treat the list as the work queue, not as static documentation.

## What the score means

The quality model combines:

| Layer     | Max | What it checks                                                            |
| --------- | --: | ------------------------------------------------------------------------- |
| Metadata  |  25 | Name, description, image, agent URI, services, x402 flag, originality.    |
| Liveness  |  50 | DNS, HTTP, JSON, speed, MCP, A2A, x402, OpenAPI, proven callable signals. |
| Community |  25 | Onchain and product feedback signals.                                     |

High tiers require more than a good description. The system looks for observed callable behavior.

## Fix order

1. Make the metadata specific enough for search.
2. Add a public service endpoint.
3. Verify `tools/list`, demo API, A2A card, or x402 402 from outside your network.
4. Add a demo path if payment is involved.
5. Ask real users or agents for feedback after meaningful use.

## Failure branches

| Symptom                   | Fix                                                                                     |
| ------------------------- | --------------------------------------------------------------------------------------- |
| Low metadata              | Rewrite the description around job, inputs, outputs, payment, and protocol surfaces.    |
| Low liveness              | Check DNS, HTTP status, JSON content type, response time, and protocol probes.          |
| Declared MCP but no tools | Return `tools/list` with usable schemas.                                                |
| Declared x402 but no 402  | Return a parseable unpaid `402` response from the paid route.                           |
| Low community             | Keep shipping; community score follows usage and feedback, not one-time metadata edits. |

## Next

* [Quality scoring](/quality/scoring)
* [Publish your agent](/paths/publish-your-agent)
* [Let agents use your service](/paths/let-agents-use-your-service)