Skip to main content
Glama

get_intake_questions

Read-only

Free. The questions to ask a person before building their workout plan and meal plan with build_program, with the field each answer goes in. Also lists the other MTFIT tools and prices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: that calls are free (cost/latency trade-off is negligible, so it can be called liberally) and that the response bundles a second dataset, the tool catalog and prices, which an agent would not otherwise expect from a name like 'get_intake_questions'.

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 short sentences, front-loaded with the cost note and then the primary purpose, with the secondary catalog payload disclosed last. Nothing is padded, though the fragment 'Free.' and the run-on middle sentence make it slightly choppier than it needs to be.

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 input parameters and no output schema, the description carries the burden of describing the response, and it does so at a useful level: questions plus 'the field each answer goes in', plus the tool/price list. It stops short of describing the exact response shape, but it is sufficient for an agent to decide to call it.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool applies. The description sensibly spends its words on what the tool returns instead.

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?

The description names the specific resource returned (the intake questions to ask a person before building a workout/meal plan) and ties it to a named sibling, build_program. It also discloses a secondary payload (the MTFIT tool list and prices). The verb is implicit ('the questions to ask... also lists') rather than a direct 'returns', but an agent can still tell exactly what comes back and how this differs from build_program.

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?

The phrase 'before building their workout plan and meal plan with build_program' establishes an explicit ordering: call this first, then build_program. No exclusions are stated (e.g. what to do for an existing client), so it falls short of a full when/when-not treatment, but the sequencing cue is clear.

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