Skip to main content
Glama

Care history

get_care_history
Read-onlyIdempotent

Wraps GET /api/house/history. Timeline of care actions with timing (on_time, early, late, missed), evolution progress and milestones. format=markdown returns a readable narrative.

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_care_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for creature_id.
limitNoMax care log entries to return.
formatNoResponse format. 'markdown' returns a text/markdown narrative; default is JSON.
offsetNoCare log entries to skip, for paging back through a long history.
creature_idNoUUID of the creature whose history to fetch.

Output Schema

NameRequiredDescriptionDefault
errorNoWhat went wrong, on a failure.
statsNoTotals across the care log.
detailsNoMore about a failure, when there is more to say.
messageNoA human and agent readable note about what just happened.
care_logNoEvery act of care, newest first.
creatureNoThe creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read.
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.
evolution_historyNoEach stage this creature has passed through.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "One creature's full care record.",
      +  "properties": {
      +    "care_log": {
      +      "description": "Every act of care, newest first."
      +    },
      +    "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."
      +    },
      +    "evolution_history": {
      +      "description": "Each stage this creature has passed through."
      +    },
      +    "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"
      +    },
      +    "stats": {
      +      "description": "Totals across the care log."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds genuine content detail (timing buckets, evolution progress, milestones) and the markdown narrative behavior. It says nothing about pagination limits, ordering, or empty-history behavior.

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 short sentences with the resource front-loaded and no filler. The opening 'Wraps GET /api/house/history' is endpoint trivia that adds little for an agent choosing a tool, but it is brief and does not obstruct the rest.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not needed, and the description covers the domain content well. However, with zero required parameters and an id/creature_id alias pair, an agent gets no guidance on what happens when the identifier is omitted or which of the two to supply.

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%, so all five parameters are already documented, including the format enum and the offset/limit paging pair. The description's only parameter statement (format=markdown returns a narrative) restates what the schema already says, and it never addresses the id/creature_id alias ambiguity.

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?

States a specific resource and scope: 'Timeline of care actions with timing (on_time, early, late, missed), evolution progress and milestones.' An agent knows exactly what data comes back. It does not name or distinguish itself from siblings such as get_creature_status or get_creature_preferences, which keeps it from 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 only implied by the content list — an agent can infer 'use this to review a creature's care past,' but there is no explicit when-to-use, when-not, or pointer to an alternative view of related data. No exclusions or prerequisites are stated.

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.