Skip to main content
Glama
Sign In
gingr-mcp

gingr-mcp

by shashicandev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List animals

gingr_list_animals
Read-only

Retrieve a list of pets registered at the facility, including species, breed, age, and owner information. Filter by owner to analyze pet population demographics.

Instructions

List animals (pets) registered at the Gingr facility — species, breed, age, owner, and notes. Use to analyze the pet population (breed mix, size distribution, etc.).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (1–200, default 50)
owner_idNoFilter to animals belonging to a specific owner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds context about the data fields (species, breed, etc.) but lacks details on pagination, rate limits, or response behavior. Safe but minimal added value.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose. Every word adds value with no fluff.

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?

For a simple list tool with no output schema, the description covers purpose, typical fields, and usage intent. Missing details on ordering or empty results, but adequate for an agent familiar with list endpoints.

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 coverage is 100% (both limit and owner_id documented). The description does not add new meaning to parameters; it mentions output fields instead. Baseline 3 applies.

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?

Clearly states the verb 'list' and resource 'animals (pets)' with specific attributes (species, breed, age, owner, notes). The usage hint differentiates from siblings like gingr_list_appointments by focusing on pet population analysis.

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?

Provides explicit context for use ('analyze the pet population'), but does not mention when not to use it or alternatives among siblings. Still, the guidance is clear and relevant.

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