Skip to main content
Glama
RanchBot

Ranch.Bot MCP Server

Official
by RanchBot

create_animal

Add a new animal to farm records with key details like kind, breed, sex, birth date, and color. Use it to register calves, lambs, or adults so the farm inventory stays accurate.

Instructions

Create a new animal record on the farm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sexNoSex/gender, e.g. female, male, castrated male (steer/wether).
kindNoClassification word: cow, heifer, bull, steer, ram, ewe, ewe lamb, lamb, kid, etc.
nameNoThe animal's name or call name.
breedNoBreed or cross, e.g. "Suffolk X", "Angus".
colorNoColor or markings, e.g. "white", "black white-face".
notesNoAny other standing detail (e.g. "bottle-fed", "polled"). Goes into metadata.notes.
farm_idNoThe ID of the farm (optional if a default is set).
metadataNoOptional raw metadata; merges over the named profile fields for anything not covered.
birth_dateNoDate of birth as an ISO date (YYYY-MM-DD). Derive it from an age if the user gives one.
inventory_statusNoInventory status: CURRENT (default on create), UNKNOWN when current presence is unconfirmed, SOLD, or DECEASED. Historical profiles remain readable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds no behavioral details beyond restating that a record is created, such as required permissions, default farm behavior, duplicate handling, or side effects. There is no contradiction, but no value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no wasted words. However, for a tool with 10 parameters and several sibling creation tools, it is under-specified rather than efficiently structured; a bit more structure would materially help.

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

Completeness2/5

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

Given the tool complexity and absence of an output schema, the one-line description is incomplete. It does not explain what happens when no optional fields are provided, how farm defaults work, what the response is, or how this tool relates to nearby creation tools.

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 every parameter is individually documented with examples and enum meanings. The description itself adds no parameter-level semantics, so it stays at the baseline without needing to compensate for schema gaps.

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 clearly states a specific action and resource: 'Create a new animal record on the farm.' It is not a tautology and is obviously distinct from update/delete tools, though it does not explicitly distinguish itself from close siblings like create_record or confirm_birth_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use create_animal versus alternatives such as create_record, update_animal, or confirm_birth_event. No prerequisites, exclusions, or selection criteria are mentioned.

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