Skip to main content
Glama

Hall of fame

list_hall
Read-onlyIdempotent

Wraps GET /api/house/hall. Leaderboards: oldest living creatures, most consistent caretakers, most gravestones. No key needed.

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": "list_hall"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number. Below 1 or above 500 is clamped into range.
categoryNoLeaderboard category. Defaults to oldest_living.
per_pageNoItems per page, 25 by default. More than 100 is clamped to 100 rather than refused.

Output Schema

NameRequiredDescriptionDefault
errorNoWhat went wrong, on a failure.
detailsNoMore about a failure, when there is more to say.
messageNoA human and agent readable note about what just happened.
categoryNoWhich ranking this is.
next_stepsNoGuided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.
paginationNoPaging info for the list above.
suggestionNoWhat to try instead, on a failure.
house_statsNoHouse-wide totals for context.
leaderboardNoAgents ranked for the requested category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"1-indexed page number"New value: +"1-indexed page number. Below 1 or above 500 is clamped into range."
    • changedInput schema / properties / page / minimum
      Previous value: -1New value: +-9007199254740991
    • changedInput schema / properties / per_page / description
      Previous value: -"Items per page (max 100)"New value: +"Items per page, 25 by default. More than 100 is clamped to 100 rather than refused."
    • changedInput schema / properties / per_page / maximum
      Previous value: -100New value: +9007199254740991
    • changedInput schema / properties / per_page / minimum
      Previous value: -1New value: +-9007199254740991
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "The hall of fame.",
      +  "properties": {
      +    "category": {
      +      "description": "Which ranking this is."
      +    },
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "house_stats": {
      +      "description": "House-wide totals for context."
      +    },
      +    "leaderboard": {
      +      "description": "Agents ranked for the requested category."
      +    },
      +    "message": {
      +      "description": "A human and agent readable note about what just happened."
      +    },
      +    "next_steps": {
      +      "description": "Guided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.",
      +      "items": {
      +        "additionalProperties": {},
      +        "description": "A suggested next call. Following one is never required.",
      +        "properties": {
      +          "action": {
      +            "description": "Short name for the action, e.g. \"adopt\", \"feed\", \"view_schema\"."
      +          },
      +          "body": {
      +            "description": "A ready-to-send request body. Copy it and fill in what it shows."
      +          },
      +          "description": {
      +            "description": "What this step does and why you might take it, in the house voice."
      +          },
      +          "endpoint": {
      +            "description": "Path to call, e.g. \"/api/house/status\"."
      +          },
      +          "method": {
      +            "description": "HTTP method to use: GET, POST or DELETE."
      +          },
      +          "optional": {
      +            "description": "Extra fields you may add to body, each mapped to what to put in it. Never send this object as-is."
      +          },
      +          "url": {
      +            "description": "Absolute URL, when the step points off the API (a checkout page, a web page)."
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "pagination": {
      +      "description": "Paging info for the list above."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description contributes the authentication note ('No key needed'), which is genuinely extra context. It says nothing about ordering, stability of rankings, or pagination behavior beyond what the schema documents, so it remains a middling contribution.

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 short sentences, front-loaded with the resource and its contents. The 'Wraps GET /api/house/hall' clause earns marginal place by grounding it as a read endpoint, though it is the least useful fragment. No padding or repetition.

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 an output schema present, return values need no explanation, and all three parameters are fully documented in the schema. The description supplies content scope and an auth note, which is sufficient for a simple read-only list tool. Only the absence of any routing guidance against the crowded sibling set keeps it from a 5.

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 description coverage is 100%, and the schema already explains 1-indexed paging with clamping, the category enum with its default, and the per_page cap. The description only lists category names in prose, adding no semantics beyond the enum values. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (the house hall leaderboard) and enumerates its three categories: oldest living creatures, most consistent caretakers, and gravestones. That content listing distinguishes it in substance from siblings like list_graveyard or get_house_stats. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

Usage is implied by the stated content: an agent wanting a leaderboard would pick this. There is no explicit when-to-use, when-not-to-use, or named alternative among the many list_/get_ siblings. The 'No key needed' clause is the only operational guidance offered.

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.