Skip to main content
Glama

Go-To Local Missed-Call Calculator

What is an AI employee?

what_is_an_ai_employee
Read-onlyIdempotent

Explains what an AI employee is at Go-To Local, a Denver company that builds and runs AI employees for local service businesses in Colorado, North Carolina and South Carolina: the five employees, the two jobs they fall under (answer every customer, and reach out to new customers) and where each stands today, the founding pilot price, what the company says it will not do, and that an AI employee tells callers at the start that it is an AI assistant. The text is taken from the Go-To Local website (https://gotolocalai.com/employees) and reflects the site as of its last deploy. No input.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds meaningful context beyond them: the content is a verbatim snapshot of the Go-To Local website and reflects the site as of its last deploy, warning the agent the text may be stale. It does not state the return format (plain text vs. markdown), which keeps it from a 5.

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?

The definition is front-loaded with the core purpose before the enumerated content, and the trailing "No input." is a useful, compact constraint. The middle enumeration is a long run-on list that could be tightened, but every item conveys what the caller will receive.

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?

There is no output schema, so the description must describe the payload, and it does so by listing the topics the returned text covers plus its source URL and freshness. That is sufficient for an agent to decide correctly whether to call it; only the response format is left unspecified.

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?

With zero parameters, the baseline is 4. The explicit "No input." correctly sets the expectation that no arguments are accepted, which matches the empty properties object in 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?

The description opens with a specific verb+resource ("Explains what an AI employee is at Go-To Local") and then enumerates the exact content covered: the five employees, the two jobs, pilot pricing, exclusions, and the AI disclosure. An agent knows precisely what this tool returns. It does not, however, differentiate itself from the sibling missed_call_cost, so it stops short of a 5.

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?

Usage is implied rather than stated: this is a static informational lookup, and "No input" signals it is a zero-argument call. There is no explicit when-to-use framing and no mention of when the sibling missed_call_cost would be the better choice instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources