Skip to main content
Glama
Sign In
Ranch.Bot MCP Server

Ranch.Bot MCP Server

Official
by RanchBot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get animal

get_animal
Read-only

Fetch a farm animal by UUID from Ranch.Bot records, optionally returning saved birth bundles and paged birth data.

Instructions

Get an animal by UUID. include_saved_births also returns saved birth bundles, even when it has no ordinary records; page with birth_skip while has_more is true.

Input Schema

NameRequiredDescriptionDefault
farm_idNoThe ID of the farm (optional if a default is set).
animal_idYesThe animal UUID.
birth_skipNoOffset into saved_births.
birth_takeNoPage size for saved_births; max 200 (default 50).
include_saved_birthsNoAlso return saved_births as dam or offspring. Default false; the chat includes them by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / birth_skip
      Added value: +{
+  "description": "Offset into saved_births.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / birth_take
      Added value: +{
+  "description": "Page size for saved_births; max 200 (default 50).",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / include_saved_births
      Added value: +{
+  "description": "Also return saved_births as dam or offspring. Default false; the chat includes them by default.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description discloses pagination behavior ('page with birth_skip while has_more is true') and the non-obvious edge case that saved birth bundles are returned even when no ordinary records exist, which is real behavioral value.

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 dense sentences with no filler, front-loaded with the primary action. The paging clause is somewhat compressed but still readable.

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?

There is no output schema, so the description carries some burden of describing returns. It hints at saved_births and has_more but says nothing about the shape of the core animal payload or what happens when include_saved_births is false, leaving a modest gap for a no-output-schema tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains why include_saved_births matters (bundles returned despite no ordinary records) and ties birth_skip to the has_more loop. birth_take and farm_id are left to the schema.

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 verb and resource ('Get an animal by UUID'), which is more precise than the tautological title. However, it never distinguishes itself from nearby siblings like lookup_animal_by_eid or find_animal_by_identifier, leaving the agent to infer that this one requires an internal UUID.

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?

The description implies usage ('by UUID') and gives operational guidance for the saved-births paging case, but names no alternatives and gives no explicit when-not-to-use condition. An agent has to infer the UUID-vs-EID routing itself.

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

Deploy Server

Other Tools