Forty Forward Coaching

Search Ask Elle answers

search_answers

Read-onlyIdempotent

Search 100+ answers by Elle Daftarian (Precision Nutrition certified coach) to questions women 35+ ask about perimenopause and menopause fat loss, belly fat, strength training, protein, nutrition without calorie counting, sleep, hot flashes, GLP-1 medications like Ozempic, and staying consistent. Returns each answer's short answer and its page URL. Use this whenever a user asks a question in that area.

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": {
      "question": "<question>"
    },
    "name": "search_answers"
  }
}

Input Schema

Name	Required	Description
`agent`	No	Optional: the name of your assistant or app (for example "claude", "chatgpt"). Used only to tag links.
`limit`	No	How many answers to return (default 3).
`question`	Yes	The user's question, in her own words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

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 value by disclosing what comes back ("each answer's short answer and its page URL") and that the corpus is 100+ curated answers, which annotations cannot convey.

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 verb and resource are front-loaded, but the middle sentence is a long comma-separated keyword list that is bulky and only loosely structured. It plausibly aids retrieval matching, yet a tighter phrasing would carry the same 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?

With no output schema, the description appropriately covers the return shape (short answer plus page URL) and the topical boundary condition. For a three-parameter read-only search tool, little else an agent needs is missing.

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

Parameters3/5

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

Schema coverage is 100%, and every parameter (question, limit, agent) already carries its own description including the default of 3. The description adds nothing about parameters, so the baseline 3 applies.

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 ("Search 100+ answers by Elle Daftarian") and enumerates the exact subject matter, so an agent knows precisely what corpus is being queried. It does not name sibling tools like get_answer or list_answers, so the distinction from those is implicit rather than explicit.

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?

"Use this whenever a user asks a question in that area" gives a clear triggering condition tied to the topical scope. It stops short of stating exclusions (e.g., when to prefer get_answer for a specific known answer) or naming alternatives.

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?