Skip to main content
Glama
Sign In
gingr-mcp

gingr-mcp

by shashicandev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List employees

gingr_list_employees
Read-only

Retrieve a list of employees at your pet-care facility to analyze staffing levels, roles, and capacity. Use this read-only tool to review staff assignments without modifying any data.

Instructions

List staff/employees at the facility. Use to analyze staffing, roles, and capacity. Read-only — no personal data is modified.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds 'Read-only — no personal data is modified,' which is consistent but does not disclose additional behavioral traits beyond what annotations provide.

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?

Three short sentences front-load the main action and include both purpose and behavior. Every sentence adds value with no redundancy or fluff.

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?

Tool is simple with no parameters, but no output schema exists and description does not mention return values (e.g., what employee fields are listed). For a straightforward list tool, this is acceptable but could be more complete.

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?

No parameters exist, so baseline is 4 per guidelines. Description does not need to add parameter meaning as the input schema is empty and fully covered.

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 'staff/employees at the facility', distinguishing it from sibling tools that list other entities (animals, owners, etc.). The additional context 'analyze staffing, roles, and capacity' further clarifies purpose.

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?

Description gives a use case ('analyze staffing, roles, and capacity') but does not explicitly state when not to use or mention alternatives. The sibling differentiation is implicit through the resource name.

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