Forty Forward Coaching

Start an application

start_application

Read-onlyIdempotent

Give the user her next step to work with Forty Forward: the short video from Chris and Elle, then the application for a free call with Coach Chris. Coaching is application only; there is no checkout. This tool does not submit anything or collect her details; she applies herself.

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

Input Schema

Name	Required	Description	Default
`agent`	No	Optional: the name of your assistant or app (for example "claude", "chatgpt"). Used only to tag links.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the tool submits nothing and collects no details, the user applies herself — exactly the kind of side-effect clarification an agent needs before calling a funnel 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?

Two sentences, front-loaded with the user-facing outcome, then the constraint. Every clause carries information; only the slightly conversational phrasing ('the short video from Chris and Elle') adds words without adding agent-relevant meaning.

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-optional-param, no-output-schema tool, the description covers what it returns (a next step: video then application), what it does not do (no submission, no data collection), and the no-checkout constraint. Sufficient for correct invocation, with only the sibling routing left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one optional parameter exists and the schema documents it at 100% coverage, including its purpose (tagging links) and an example. Nothing is left for the description to compensate for, so the baseline is fully met.

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 concrete outcome: hand the user her next step — the short video from Chris and Elle, then the application for a free call with Coach Chris. The resource and sequence are specific, though the verb 'give the next step' is softer than a crisp action verb and it never names a sibling to contrast with.

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?

'Coaching is application only; there is no checkout' clarifies the business context and rules out a payment path, which implies when this tool applies. But it gives no explicit trigger for choosing this over check_fit or get_program_overview, leaving the agent to infer the moment to call it.

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

All Forty Forward Coaching tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?