Skip to main content
Glama

Protein calculator

protein_calculator
Read-onlyIdempotent

Daily protein range in grams from body weight and whether the person exercises most weeks, and the amount at each eating time when the number of eating times a day is given. Weight (weight_kg or weight_lb) is also required.

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": {
      "exercise": "<exercise>"
    },
    "name": "protein_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesNoOptional: eating times a day, 1 to 6
exerciseYesExercises most weeks
weight_kgNoWeight in kilograms, 25 to 400
weight_lbNoWeight in pounds, instead of weight_kg

Output Schema

NameRequiredDescriptionDefault
noteNoA line instead of a number, when no number applies
pageYes
toolYes
inputsYesThe inputs as understood, in metric units
methodYesHow the answer is worked out
resultNo
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description does add genuine behavior beyond them: the per-eating-time output only appears when the number of eating times is supplied, and weight is claimed to be required even though the schema marks only exercise as required. That last point is a schema tension (not an annotation contradiction) and actually helps the agent supply the right inputs.

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?

It is a single dense sentence of about forty words with stacked subordinate clauses ('and ... and ...'), which makes the conditional logic harder to parse than two short sentences would. Nothing is padding, but the structure is not front-loaded around the action.

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

Completeness3/5

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

With an output schema present, the description need not detail return values, and annotations handle safety, so what remains is mostly adequate. Gaps: no statement that weight_kg and weight_lb are mutually exclusive, and no hint about which factors drive the range. An agent could still call it correctly, but marginally.

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%, so the baseline is 3 and the schema already documents ranges, units and the times 1–6 bound. The description slightly reinforces meaning by noting weight_kg or weight_lb as alternatives and tying `times` to the conditional per-meal output, but it adds no syntax, exclusivity rule, or unit-conversion guidance beyond that.

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 domain (dietary protein) and states the two outputs precisely: a daily protein range in grams and a per-eating-time amount. The 'protein' subject and gram units distinguish it from bmi_calculator, calorie_calculator and water_intake_calculator without needing to name them. It falls short of 5 only because it is phrased as an output spec rather than a verb+resource action statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusion against the sibling calculators, even though a protein calculator sits in a family where choosing the wrong one is the main failure mode. The only implicit guidance is that the person's exercise habit is a required input. An agent must infer the selection criteria on its own.

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