Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Start Interest Interview

start_interest_interview

Returns an interview script that guides researchers through defining their research interests or news topics, so they can set up what to follow.

Instructions

Get the script for interviewing the researcher about their interests.

Call this when the researcher wants help defining their research interests or
news topics — typically arriving from the "Set up my interests" button on the
Metis Systems surface, which opens a conversation asking for exactly this.

Returns the full interview to follow. It lives here rather than in the button's
deep link because a `claude://` URL carrying the whole script came to 3,222
characters, over the ~2,048-character limit Windows protocol handlers accept —
it would have been truncated or dropped silently. Keeping the script here also
means it is maintained in one place instead of duplicated in a template.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it says the tool returns the full interview to follow, implying a read with no side effects, and explains the design decision behind hosting the script (protocol URL length limits). It does not explicitly confirm there are no state changes or mention any logging/telemetry.

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?

Purpose and trigger are front-loaded in the first two sentences, which is good structure. The final sentences about the 3,222-character claude:// URL are engineering rationale that does not help an agent invoke the tool and could be trimmed without loss.

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 tool with an output schema, the description covers what it returns and when to call it, which is sufficient to invoke correctly. The only gap is the absent explicit statement of side effects, which matters somewhat given there are no annotations.

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 is nothing for the description to disambiguate and the baseline of 4 applies. The schema is empty and fully self-explanatory.

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 states a specific verb and resource: it fetches the interview script the agent should follow when helping a researcher define interests. It implicitly separates itself from siblings like set_research_interests or suggest_interests_from_work by clarifying that it returns a script rather than saving anything, but no sibling is named outright.

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?

It gives a concrete trigger — 'Call this when the researcher wants help defining their research interests or news topics' — and even names the UI entry point ('Set up my interests' button). No explicit when-not condition or named alternative tool is provided, so it stops short of full routing guidance.

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