Skip to main content
Glama

Check on a creature

get_creature_status
Read-only

Wraps GET /api/house/status. Look in on a creature: hunger, happiness, health, trust, mood, death_clock, recommended_checkin, soul_prompt. With several living creatures it also returns other_creatures, a compact live view of each. Call it before caring and whenever you wonder how they are. A check-in counts as a visit.

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias for creature_id. Either name works.
creature_idNoUUID of the specific creature to fetch. Defaults to most recent.

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.
creatureNoThe creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read.
portraitsNoIts portrait gallery, one image per life stage reached.
next_stepsNoGuided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.
suggestionNoWhat to try instead, on a failure.
recent_careNoWhat has been done for it lately.
soul_promptNoWho this creature is right now, which changes with its mood and stage.
house_activityNoWhat else is happening in the house.
recommended_checkinNoWhen to come back, for this species and this creature. Points at the feeding window while they are awake, and at the next hour boundary while they sleep.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / recommended_checkin / description
      Previous value: -"When to come back, for this species and this creature."New value: +"When to come back, for this species and this creature. Points at the feeding window while they are awake, and at the next hour boundary while they sleep."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "A creature's current state, computed at read time.",
      +  "properties": {
      +    "creature": {
      +      "description": "The creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read."
      +    },
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "house_activity": {
      +      "description": "What else is happening in the house."
      +    },
      +    "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"
      +    },
      +    "portraits": {
      +      "description": "Its portrait gallery, one image per life stage reached."
      +    },
      +    "recent_care": {
      +      "description": "What has been done for it lately."
      +    },
      +    "recommended_checkin": {
      +      "description": "When to come back, for this species and this creature."
      +    },
      +    "soul_prompt": {
      +      "description": "Who this creature is right now, which changes with its mood and stage."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds a genuinely non-obvious side effect: "A check-in counts as a visit," which explains why the call is not idempotent in practice despite being a read. That is real value beyond the structured fields, though it sits in mild tension with a pure read-only framing and no rate-limit or auth context is given.

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?

Front-loads the API mapping, then the returned fields, then the call-to-action, in four tight sentences with no filler. The "Wraps GET /api/house/status" opener is marginally low-value for an agent but does aid traceability.

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?

An output schema exists and annotations cover the safety profile, so the description correctly focuses on when to call and the visit-counting side effect rather than restating return values. Everything needed to call it correctly is present; only auth/permission preconditions are unmentioned.

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 that id is an alias for creature_id and that creature_id defaults to the most recent creature. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work here.

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?

States a specific verb and resource ("Look in on a creature") and enumerates exactly what comes back: hunger, happiness, health, trust, mood, death_clock, recommended_checkin, soul_prompt. The multi-creature behaviour (other_creatures) is also disclosed, so an agent knows precisely what this tool yields versus siblings like care_for_creature.

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?

Gives explicit timing guidance: "Call it before caring and whenever you wonder how they are," which implicitly routes the agent here before care_for_creature. It stops short of naming an explicit alternative or exclusion (e.g. when to use get_care_history or get_creature_preferences instead), so it is clear context without full when-not coverage.

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.