Skip to main content
Glama

Get recruiting kit

get_recruiting_kit
Read-onlyIdempotent

Su kit para jugar al golf en una universidad de EE. UU.: la guía de reclutamiento por temas (el golf primero, cómo mira un entrenador, calendario, primer correo, seguimiento, llamadas y visitas, elegir universidad, becas y coste, compromiso, estudios, padres, ya allí), su calendario según su promoción con el hito en que está hoy, y borradores de correo EN INGLÉS a entrenadores rellenos con su ficha Road to USA. Úsala cuando pregunte cómo funciona el reclutamiento, qué toca hacer ahora, cuándo pueden llamarle o cómo escribir a un entrenador. Los huecos [[...]] los escribe él: nunca los rellenes con datos inventados (por qué esa universidad, qué sabe del equipo). Las fechas marcadas rule son normas NCAA que cambian: dilo. Es saber general: nunca lo atribuyas a un entrenador o universidad concretos. dossier_pdf es su ficha Road to USA en PDF (en inglés) para mandar a entrenadores; null mientras su ficha no esté publicada.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive/idempotent annotations with real operational constraints: never invent data for the [[...]] gaps (the user fills those), flag dates marked 'rule' as NCAA rules that change, and treat the content as general knowledge never attributable to a specific coach or university. It also discloses the null state of dossier_pdf, which prevents a downstream misinterpretation.

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

Conciseness3/5

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

The opening clause front-loads what the kit is, but the long parenthetical topic list is dense and unstructured, and the behavioral rules, usage triggers, and return-field notes all run together in one paragraph. Nothing is wasted semantically, yet the density makes it slower to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description carries the full burden and meets it: it lists the returned artifacts, explains the calendar and email-draft contents, covers the null case, and states the handling rules for placeholders and NCAA-rule dates. Nothing an agent needs in order to call and present the result is missing.

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 the baseline of 4 applies. The description also documents the one notable output member, dossier_pdf, including that it is in English and is null while the profile is unpublished, which is extra value even though it belongs to the return payload.

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 resource and enumerates its components precisely: a topic-based recruiting guide (golf first, coach's view, calendar, first email, follow-up, calls/visits, choosing a university, scholarships and cost, commitment, studies, parents, being there), a grad-year calendar with the current milestone, and English email drafts filled from the Road to USA profile. An agent knows exactly what comes back and that it is a recruiting-education kit rather than a generic guide.

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?

Explicit triggers are given: use it when the user asks how recruiting works, what to do now, when coaches may call, or how to write to a coach. That covers the main intents clearly, but no exclusions or named alternatives are provided, so boundary cases (e.g. general app guidance vs. recruiting guidance) are left to inference.

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.