Skip to main content
Glama

get_profile

Read-onlyIdempotent

Retrieve the athlete’s health profile—age, birth year, biological sex, blood type, wheelchair use, move mode, and skin type—from local Apple Health data.

Instructions

The athlete's characteristics as Health has them: age and birth year, biological sex, blood type, wheelchair use, move mode, skin type.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The phrase 'as Health has them' adds a useful hint that values reflect what Apple Health stores and may therefore be unset or stale, but nothing is said about permissions, error behavior, or missing-data handling. With annotations carrying the safety load, a 3 is appropriate.

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?

A single sentence with no padding; the resource is front-loaded and the attribute list follows. Every listed field earns its place since it doubles as return-value documentation. The fragmentary syntax without a leading verb is the only rough edge.

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 zero-parameter read with no output schema, the enumerated field list effectively documents what comes back, which is the main thing an agent needs. Absent are notes on nullability or units, which matter somewhat for an untrusted, possibly incomplete Health-backed record.

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 are no parameter semantics to explain and the baseline of 4 applies. No schema-level parameter documentation is needed or missing.

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?

Names the resource (the athlete's profile/characteristics) and enumerates the exact attributes returned: age, birth year, biological sex, blood type, wheelchair use, move mode, skin type. This is enough to distinguish it from measurement-oriented siblings like get_vitals. It is a noun phrase rather than a verb+resource statement, so it falls short of the crispest form.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The field enumeration implicitly routes the agent: static demographics come here, whereas dynamic measurements belong to get_vitals. That inference is reasonable but left entirely to the reader.

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