Skip to main content
Glama

get_user_profile

Retrieve the user's identity, research interests, news topics, and active model to personalize interactions from the start.

Instructions

Return the user's identity, interests, and active model preference.

Call this at the start of any personalised run to understand the user's
topics and news signals to prioritise.

Returns JSON with:
- display_name: user's display name (set via /metis_config)
- role: professional role (e.g. "Senior researcher · public health")
- interests: list of research interest tags (e.g. ["sleeping sickness", "multilevel models"])
- news_topics: list of news monitoring topics (e.g. ["WHO surveillance", "AI governance"])
- active_model: current default model slug (haiku / sonnet / opus)

Usage pattern:
  profile = json.loads((await get_user_profile())[0].text)
  interests = profile['interests']   # → ["sleeping sickness", "multilevel models"]
  news_topics = profile['news_topics']  # → ["WHO surveillance", "AI governance"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It fully discloses the return fields with examples and a parsing pattern. No side effects or destructive behavior implied; tool is read-only.

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?

Description is somewhat lengthy but well-structured: purpose first, then usage, then detailed output with examples, and a usage pattern. Every sentence adds value, front-loaded with key information.

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?

Given zero parameters, high schema coverage, and presence of output schema, the description is complete. It covers what the tool does, when to use it, and exactly what is returned with usage example.

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?

No parameters exist, so baseline is 4. Description adds no parameter info because none needed; schema coverage is 100%.

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?

The description clearly states the tool returns the user's identity, interests, and active model preference with a specific verb and resource. It distinguishes itself from sibling tools by being unique for profile retrieval.

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?

Explicitly recommends calling at the start of any personalised run to understand user topics and news signals. Does not mention when not to use or alternatives, but given no parameters and no competing tool, this is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server