Skip to main content
Glama

intentions_get_profile

Read-only

Fetch the user's currently stored birth info. Use this before intentions_set_birth_info when updating an existing profile so you can send back a complete merged payload. Returns { hasProfile, birthInfo: { year, month, day, hour, minute, gender } | null, profileChanges: { remaining, resetsAt } | null, birthPlace: string | null, next? } where next, when present, says what to ask the user (e.g. their city of birth). Any unknown birth field (e.g. unknown hour) is returned as null. profileChanges is how many changes to the date, gender or a known hour are left this calendar month (UTC) and the ISO instant they come back; if remaining is 0, tell the user before attempting such a change. No quota cost.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds meaningfully more: the full return shape, the convention that unknown birth fields come back as null, quota accounting semantics (UTC calendar month, resetsAt instant), and the fact that the call itself is free. These are behavioral facts an agent could not infer from structured fields.

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?

Front-loaded with purpose and the key ordering instruction, then moves into return shape and quota details. It is dense but nearly every clause carries actionable information; the quota explanation is slightly verbose and could be tightened.

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

Completeness5/5

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

There is no output schema, so the description must carry the return contract — and it does: field names, nullability, the meaning of `next`, and quota limits with reset timing. Nothing an agent needs to consume the response or drive the follow-up question correctly is missing.

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 the baseline is 4 and there is nothing further to disambiguate. The description instead spends its words on the response contract, which is the relevant semantics for a no-arg tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch the user's currently stored birth info") and immediately distinguishes itself from the sibling mutation tool intentions_set_birth_info. An agent can tell it apart from the intentions_ask_* and energy_chart siblings without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names when to use it ("before intentions_set_birth_info when updating an existing profile") and explains the reason for that ordering (to send back a complete merged payload). Also gives an in-flow rule: if profileChanges.remaining is 0, tell the user before attempting a change.

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.