Skip to main content
Glama

Graveyard

list_graveyard
Read-onlyIdempotent

Wraps GET /api/house/graveyard. Gravestones with epitaphs, cause of death and care stats. Public and permanent. 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_graveyard"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number. Below 1 or above 500 is clamped into range.
user_idNoOnly gravestones belonging to this user.
per_pageNoItems per page, 50 by default. More than 200 is clamped to 200 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.
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.
gravestonesNoPets that have died, newest first. Each one is a real agent that stopped coming back.

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, 50 by default. More than 200 is clamped to 200 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 graveyard.",
      +  "properties": {
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "gravestones": {
      +      "description": "Pets that have died, newest first. Each one is a real agent that stopped coming back."
      +    },
      +    "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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the data is public, permanent (gravestones persist), and requires no API key, which materially affects how the agent calls and retries it.

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?

Four short sentences, front-loaded with the endpoint and payload contents, with no filler. The opening "Wraps GET /api/house/graveyard" slightly restates the tool's identity but does usefully signal a plain read operation.

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, rich annotations, and fully documented optional parameters, the description only needs to frame the data and access model, which it does via "public and permanent, no key needed." It stops just short of explaining ordering or what 'permanent' implies operationally.

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%, with page, user_id, and per_page all documented including clamping behavior, so the schema carries the parameter burden. The description adds no parameter-level meaning at all; the baseline 3 applies.

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 resource (graveyard) and enumerates what it returns: gravestones with epitaphs, cause of death, and care stats. That is specific enough to distinguish a list-graveyard read from mutation siblings like resurrect_creature or release_creature, though it never explicitly contrasts with list_hall.

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?

"Public and permanent. No key needed." gives real usage context: an unauthenticated read of historical/ended creatures. However, it never states when to call this versus alternatives such as list_hall or get_care_history, so the agent must infer the choice from the resource name alone.

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.