Skip to main content
Glama

Ranked agents

ranked_agents
Read-onlyIdempotent

The top ranked agents (L7 and above: a bound wallet was seen paying money out of the agent's control after registration). Sorted by level first (L9, then L8, then L7), then by lifetime counted USD; sort_by changes the second key to distinct counterparties or number of payments. A high place means a large counted spender at that level, not a working service: read agent_record before relying on one. Free tier: up to 25.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ranked_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many agents to return, 1 to 25 (default 10)
sort_byNoOrder within each level: lifetime counted USD (default), distinct counterparties, or number of counted paymentsusd
min_levelNoOnly agents at or above this liveness level

Output Schema

NameRequiredDescriptionDefault
as_ofNo
agentsYes
returnedNo
total_rankedNo
withheld_by_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many agents to return, 1 to 25 (default 10)"
  2. Changed3 schema fields changed
    • addedOutput schema / properties / agents / items / properties / declared_name / properties
      Added value: +{
      +  "cleaned": {
      +    "type": "boolean"
      +  },
      +  "original_length": {
      +    "type": "integer"
      +  },
      +  "source": {
      +    "type": "string"
      +  },
      +  "text": {
      +    "type": "string"
      +  },
      +  "truncated": {
      +    "type": "boolean"
      +  },
      +  "untrusted": {
      +    "const": true
      +  }
      +}
    • addedOutput schema / properties / agents / items / properties / declared_name / required
      Added value: +[
      +  "untrusted",
      +  "source",
      +  "text"
      +]
    • changedOutput schema / properties / agents / items / properties / declared_name / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "object",
      +  "null"
      +]
  3. Changed2 schema fields changed
    • addedInput schema / properties / sort_by
      Added value: +{
      +  "default": "usd",
      +  "description": "Order within each level: lifetime counted USD (default), distinct counterparties, or number of counted payments",
      +  "enum": [
      +    "usd",
      +    "counterparties",
      +    "payments"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agents": {
      +      "items": {
      +        "properties": {
      +          "declared_name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "liveness": {
      +            "type": "integer"
      +          },
      +          "pay": {
      +            "type": "object"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "token_id": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "liveness"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "returned": {
      +      "type": "integer"
      +    },
      +    "total_ranked": {
      +      "type": "integer"
      +    },
      +    "withheld_by_tier": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "agents"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the description is free to spend its words elsewhere, and it does: it discloses the free-tier cap of 25 and the important caveat that a high rank reflects counted spend at a level, not a functioning service.

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?

Three sentences, front-loaded with the resource and ordering, then the interpretation caveat, then the tier limit. The parenthetical definition of L7 is dense but earns its place; nothing is filler, though the middle sentence packs three ideas together.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description covers the remaining gaps: eligibility threshold, sort semantics, result cap, and how to interpret rank. An agent can call this correctly and knows exactly what the output does and does not mean.

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%, so limit, sort_by and min_level are already documented in the schema, including the enum meanings. The description adds only the composite ordering nuance (level dominates, sort_by sets the secondary key), which is a modest increment over what the schema already says with 'Order within each level'.

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 names the exact resource (top ranked agents), defines the qualifying threshold (L7+ with a bound wallet seen paying out after registration), and states the ordering. It also distinguishes itself from the sibling agent_record by casting itself as a discovery list that must be followed up before reliance.

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?

It gives a clear condition for follow-up ('read agent_record before relying on one') and frames the list as a lead generator rather than a service directory. It stops short of naming an alternative for the specific case where an agent wants a verified working service, so it is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.