Skip to main content
Glama

Jessica Hill Holm — Coaching for Leaders Scaling

Check if Jessica Hill Holm is a good fit

check_fit
Read-onlyIdempotent

Describe a leader's or company's situation (e.g. 'Series A SaaS founder, team doubled, everything still goes through her'). Returns an honest fit assessment for Jessica Hill Holm's executive coaching and advisory work (strong / possible / not_a_fit), why, and the right next step. Returns not_a_fit when that's true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "situation": "<situation>"
    },
    "name": "check_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
situationYesThe leader's or company's situation in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower. The description still adds genuine behavioral context: the return includes a verdict, reasoning, and a recommended next step, and it explicitly warns that not_a_fit is a real possible outcome, which prevents the agent from treating this as a confirmatory tool.

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?

Three tight sentences, front-loaded with what to pass in, followed by what comes back and the honesty caveat. The parenthetical example earns its space; nothing is padded, though it could be marginally tighter.

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 single-parameter tool with no output schema, the description supplies the missing return contract (verdict, rationale, next step) and the negative-result behavior, so an agent knows what to expect. Only the routing relationship to sibling tools is left unstated.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds value by illustrating the expected freeform situation string with a realistic example ('Series A SaaS founder, team doubled, everything still goes through her'). That shapes the level of detail and framing the agent should supply beyond the schema's 'plain words' note.

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?

States a specific verb and resource: it assesses whether a described situation fits Jessica Hill Holm's executive coaching and advisory work, and names the verdict vocabulary (strong / possible / not_a_fit). An agent can tell it apart from get_coaching_offer and ask_jessicas_agent by intent, though it doesn't explicitly reference those siblings.

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?

It tells the agent how to invoke it ('Describe a leader's or company's situation') with a concrete example, but gives no explicit when-to-use versus when-not, nor does it name an alternative to route to instead (e.g., ask_jessicas_agent for general questions). Usage is implied rather than stated.

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