Skip to main content
Glama
Sign In

トゥーンエル

by com.tooneru
OverviewDiscussionsAdmin

コンテキストセット

get_context
Read-onlyIdempotent

話のコンテキストセット（作品の設定・登場人物・あらすじ・この話で分かること〈仕事・制度の問いの短い答えと条件〉・用語・出典・URL の短いまとめ）を返す。話の内容を踏まえて答える時や、続きを相談する時の前提に使う。中身は第1話からその話まで（後の話は入らない）。up_to_episode が number より前なら、ネタバレの断りを頭に付ける。

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": {
      "series_id": "<series_id>",
      "number": "<number>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes話の番号（1から）
series_idYes作品の id
up_to_episodeNo利用者が読んだ話の番号（ネタバレを避ける）。これより後の話のあらすじ・用語を省く。分からなければ省く（全部を返し、第2話以降に spoiler の印）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds important behavioral context beyond annotations: contents run from episode 1 through the requested episode, later episodes are excluded, and a spoiler notice is prepended when up_to_episode is before number.

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 front-loaded with the return value and scope, then gives usage context and spoiler handling. The parenthetical list of included context components is dense but earns its place by defining the returned content.

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?

Because there is no output schema, the description carries the burden of describing the return value, and it does so by listing the context components. It also covers the key parameter interaction and spoiler behavior, leaving no major gap for calling the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining the relationship between up_to_episode and number and the resulting spoiler-notice behavior.

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 returns a story context set and enumerates what is included, such as setting, characters, synopsis, terms, sources, and URLs. The purpose is clear, but it does not explicitly distinguish this aggregate context tool from siblings like get_episode or get_glossary.

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 clear usage context: use it as the premise when answering based on story content or when discussing continuations. It does not state when not to use it or name alternative sibling tools, so it falls short of full alternative routing guidance.

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

All トゥーンエル toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources