Skip to main content
Glama

Jessica Hill Holm — Coaching for Leaders Scaling

Jessica Hill Holm executive coaching

get_coaching_offer
Read-only

Describes Jessica Hill Holm's 1:1 executive coaching for founders, CEOs and senior leaders, and returns the link to book a free 30-minute intro call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds that it returns a booking link, which is useful return-value context, but doesn't describe side effects, auth needs, or whether the result is cached/static. Given the annotation covers read-only safety, a 3 is appropriate.

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?

Single sentence, front-loaded with what is described and the return value. No waste, though it could be arguably split for clarity, but conciseness is strong.

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 zero-parameter read-only tool with no output schema, the description tells the agent exactly what it gets (booking link) and what the offer is. It's sufficiently complete for invocation, though no output schema exists to confirm the response format.

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?

Zero parameters, so baseline is 4. The description correctly implies no inputs are needed to retrieve the offer and booking link.

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?

States a specific verb (describes/returns) and resource (Jessica Hill Holm's 1:1 executive coaching offering), plus specifies the exact return value: a booking link for a free 30-minute intro call. It's distinguishable from siblings like list_workbooks or ask_jessicas_agent, which serve different functions.

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?

The description implies usage ('asks about the coaching offer, get the booking link') but doesn't explicitly state when to use this vs ask_jessicas_agent or other siblings. An agent can infer the intent, but no exclusions or alternatives are named.

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