Skip to main content
Glama

Metis — Set Research Interests

set_research_interests

Save separate news and library research interests to tailor briefings, news tracking, and literature recommendations while keeping curiosity and scientific background distinct.

Instructions

Save the two interest lists after interviewing the person.

NEWS AND LIBRARY INTERESTS ARE SEPARATE THINGS, and either may sit entirely
outside the person's work:

  - `news_interests`    → what they want to know is HAPPENING. Drives the
    story-thread vocabulary (Metis groups news into persistent running
    stories, and a declared interest becomes a subject it can recognise), the
    News surface category tabs, and what the daily and weekly briefings
    monitor. Legitimately includes pure curiosity — following AI policy or a
    conflict closely without ever publishing on it.
  - `library_interests` → what they want a real SCIENTIFIC BACKGROUND on.
    Drives literature relevance and the knowledge layer. Slower and deeper,
    and also allowed beyond current projects: a method they intend to learn
    belongs here before it appears in any of their work.

They overlap, but the differences are the useful part. Do not collapse them.

Neither list requires the person to have any projects or articles. Someone can
join Metis with nothing set up and still have clear interests — ask, do not
infer. Call `start_interest_interview()` for the full interview.

Prefer specific, searchable terms: "coral bleaching" and "CRISPR screens"
work, "biology" is too broad to filter anything.

Args:
    news_interests: What the News surface and briefings should track.
        Omit to leave unchanged.
    library_interests: What the literature collection and knowledge layer
        should build on. Omit to leave unchanged.
    role: Optional one-line role description.
    display_name: The name to address them by. Set it when someone new tells
        you their name — without it they are greeted as "Researcher".
    mode: "replace" (default) overwrites; "add" merges into what is there.
    interests: DEPRECATED alias for `library_interests` — the old combined
        field. Accepted so existing callers keep working.
    news_topics: DEPRECATED alias for `news_interests`.

Returns:
    What was saved per list, and what each one now affects.

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

Input Schema

NameRequiredDescriptionDefault
modeNoreplace
roleNo
interestsNo
news_topicsNo
display_nameNo
news_interestsNo
library_interestsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • addedInput schema / properties / display_name
      Added value: +{
      +  "default": "",
      +  "title": "Display Name",
      +  "type": "string"
      +}
  2. Addedv0.1.5

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses what each list drives downstream (story-thread vocabulary, News tabs, briefings vs literature relevance, knowledge layer), mutation semantics (replace overwrites by default, add merges, omitting a list leaves it unchanged), and that deprecated aliases are still accepted. That is exactly the destruction/state-impact information an agent needs before writing.

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 the action and the central news/library distinction, then structured bullets, then a conventional Args block. Slightly long, and the Args section restates parts of the bullet list; the aphoristic line "Do not collapse them" is redundant with the surrounding text, though it reinforces the key risk.

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?

An output schema exists so return values need no prose, yet the description still notes what is reported back. For a 7-parameter, zero-coverage, unannotated write tool, every parameter, both deprecated aliases, the default mode, and the sibling interview tool are all accounted for.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it documents all seven parameters including the two deprecated aliases that the schema renders as plain nullable arrays with no hint of their status. Semantics added go well beyond field names, e.g. omitting a list means 'leave unchanged' and interests/news_topics map onto library/news respectively.

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 concrete verb and resource ("Save the two interest lists") and immediately disambiguates the two payload concepts, news vs library, which share a name. A reader can tell this apart from suggest_interests_from_work or start_interest_interview without inspecting either 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?

Explicit routing guidance: "Call `start_interest_interview()` for the full interview" defines the alternative and when to prefer it. It also gives a negative instruction ("ask, do not infer") and a conditional for display_name ("Set it when someone new tells you their name"), plus a term-specificity guideline with concrete examples.

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

Deploy Server

Other Tools