Skip to main content
Glama
Sign In

GradeTV

by net.gradetv
OverviewDiscussionsAdmin

Watch history

get_history
Read-onlyIdempotent

The channels that the owner watched. It shows only the channels that are available in the catalog.

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

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page. A value above 50 becomes 50.
offsetNoHow many items to skip. Use `next_offset` from the previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Itens por página. Acima de 50 é silenciosamente reduzido a 50."New value: +"Items per page. A value above 50 becomes 50."
    • changedInput schema / properties / offset / description
      Previous value: -"Quantos itens pular. Use `next_offset` da resposta anterior."New value: +"How many items to skip. Use `next_offset` from the previous response."
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / description
      Added value: +"Itens por página. Acima de 50 é silenciosamente reduzido a 50."
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"Quantos itens pular. Use `next_offset` da resposta anterior."
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral detail — that results are filtered to channels currently in the catalog — but says nothing about pagination behavior, ordering, or empty-history outcomes for a paginated read tool.

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?

Two short sentences, front-loaded with the resource definition and followed by the catalog-availability filter. Nothing is padded, though the second sentence is only marginally useful for tool selection and could be folded in.

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 two-parameter read-only list tool whose annotations cover safety and whose schema fully documents its parameters, the description covers the essentials. The remaining gap is that it says nothing about the shape of the returned data (e.g., channel objects with pagination metadata) since no output schema exists.

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?

Schema description coverage is 100%, and both parameters (limit, offset) are fully documented in the schema including the 50-item cap and the next_offset chaining hint. The description adds no parameter-level meaning beyond this, so the baseline of 3 applies.

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 specific resource — the channels the owner watched — which unambiguously identifies it as a watch-history retrieval tool. The verb is only implied ('get' from the name), and it doesn't explicitly contrast itself with siblings like chat_history or clear_history, but the resource is distinct enough for an agent to select correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the related siblings that would be natural alternatives or complements (clear_history, forget_watch, record_watch, chat_history). An agent must infer usage entirely from the title and name.

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

All GradeTV 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