Skip to main content
Glama

Set research scope

expand_research_scope
Idempotent

Add an item to the current research corpus (focused research mode only).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "media_type": "<media_type>"
    },
    "name": "expand_research_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the item to add
media_typeYesType of media to add to the research scope

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description only has to add context. The mode restriction is genuinely useful information to supply beyond the annotations, but nothing is said about what a duplicate add does, whether the item has to exist first, or what changes in the corpus. With annotations carrying the main behavioral load, a 3 is still appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that states the action first and then appends the scope qualifier. There is no filler, and the length suits a simple two-parameter tool. Nothing here should be trimmed or reordered.

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

Completeness3/5

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

With two fully documented parameters, no output schema and annotations that cover safety and idempotency, the description only needs to fill the gaps the structured data cannot. It gives the mode restriction but never explains what the research corpus is, what happens if the title is ambiguous, or what distinguishes this tool from the other add-family siblings. Adequate but visibly thin for a tool with three near-identical alternatives.

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

Parameters3/5

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

The schema is fully described (100% coverage) for both parameters, including an enum of accepted media types for `media_type`. The description adds no extra meaning, such as format expectations for `title`, whether titles must match existing library entries, or how `media_type` constrains resolution. With the schema doing all the work, this is the expected baseline of 3.

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 names a concrete verb and object: it adds an item to the current research corpus. That is a specific mutation, not a restatement of the title, and is distinguishable from siblings like add_to_list or create_list. It stops short of explaining how this differs from `add`, `add_item`, or `add_to_list`, so an agent cannot fully route on the description alone, but it also still reads as a way of adding items to a corpus and gives no indication whether it will fail or create something when the item is unknown.

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 one real usage signal, the parenthetical 'focused research mode only', which tells the agent the tool is conditional on the session mode. What the description does not do is give any positive condition for choosing this over the very similar `add` or `add_item`, and it never mentions what to do in other modes or what the alternative is. Usage guidance is implied rather than laid out, so a 3 fits.

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.

Resources