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

Ranch.Bot MCP Server

Official
by RanchBot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create animal

create_animal

Create a new animal record on a cattle or sheep farm with details such as name, kind, sex, breed, color, birth date, and inventory status for herd tracking.

Instructions

Create a new animal record on the farm.

Input 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_dateNoExact date of birth as an ISO date (YYYY-MM-DD). Supply it only when the user states the date itself. If the user gives an approximate age instead, omit this field and keep that age wording in notes; never calculate or estimate a birthday from an age. On update, leave an existing birth_date and unrelated notes unchanged.
inventory_statusNoInventory status: CURRENT (default on create), UNKNOWN when current presence is unconfirmed, SOLD, DECEASED, or NOT_MANAGED when care ended without sale or death. Historical profiles remain readable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / birth_date / description
      Previous value: -"Date of birth as an ISO date (YYYY-MM-DD). Derive it from an age if the user gives one."New value: +"Exact date of birth as an ISO date (YYYY-MM-DD). Supply it only when the user states the date itself. If the user gives an approximate age instead, omit this field and keep that age wording in notes; never calculate or estimate a birthday from an age. On update, leave an existing birth_date and unrelated notes unchanged."
    • changedInput schema / properties / inventory_status / description
      Previous value: -"Inventory status: CURRENT (default on create), UNKNOWN when current presence is unconfirmed, SOLD, or DECEASED. Historical profiles remain readable."New value: +"Inventory status: CURRENT (default on create), UNKNOWN when current presence is unconfirmed, SOLD, DECEASED, or NOT_MANAGED when care ended without sale or death. Historical profiles remain readable."
    • changedInput schema / properties / inventory_status / enum
      Previous value: -[
-  "CURRENT",
-  "UNKNOWN",
-  "SOLD",
-  "DECEASED"
-]New value: +[
+  "CURRENT",
+  "UNKNOWN",
+  "SOLD",
+  "DECEASED",
+  "NOT_MANAGED"
+]
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered and the description is consistent with it. Beyond that, the description adds no behavioral context: nothing about duplicate-name handling, what the default farm behavior is, or what the call returns for a 10-parameter write.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though it is so terse that it provides no structure for a tool with 10 parameters and a nested metadata object.

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?

For a 10-parameter creation tool with no output schema and a nested metadata object, the description is inadequate: it says nothing about defaults (farm_id optional via default, inventory_status defaulting to CURRENT), duplicate handling, or the result of creation. It leaves the agent to infer everything from the schema.

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 10 parameters (including the birth_date and inventory_status nuances) are already fully documented in the schema. The description adds no parameter meaning beyond that, so 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 a specific verb and resource ("Create a new animal record") and the farm scope, so an agent can tell it produces a new animal entity. However, it does not distinguish itself from the sibling find_or_create_animal_by_eid, which is an alternative creation path, nor from update_animal/delete_animal.

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 when-to-use or when-not-to-use guidance. The description never mentions that find_or_create_animal_by_eid is the preferred route when an EID is known, nor any prerequisite such as a default farm being set.

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