Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Update a subscribed resource

update_live_resource

Increments the live counter in a subscribed test resource and sends an update notification so you can verify whether the client re-reads the changed resource.

Instructions

Increase the counter in test://live/counter and send notifications/resources/updated for it. Subscribe first (resources/subscribe on 2025-era connections, a subscriptions/listen stream with resourceSubscriptions on 2026-07-28), then check whether the client re-reads it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
uriYes
counterYes
updatedAtYes
legacySubscribersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only establish readOnlyHint=false and idempotentHint=false; the description adds the concrete mutation (counter increment), the outbound notification it triggers, and the subscription prerequisite with version-specific mechanisms. That is meaningful context beyond the annotations, though it doesn't describe failure behavior when the subscription is absent.

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 sentences, front-loaded with the action and side effect, followed by the prerequisite and verification step. The parenthetical about subscription transports is dense but each clause carries information an agent needs.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. The description still supplies the prerequisite, the emitted notification, and how to verify the effect, leaving little an agent needs that is missing.

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?

There are zero parameters, so the standard baseline applies and the description has no parameter semantics to add. The fixed target URI is stated, which is the only input-like detail available.

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?

The description names a specific verb and target ('Increase the counter in test://live/counter') plus the emitted side effect ('send notifications/resources/updated'), so the agent knows exactly what the call mutates. No sibling tool could be confused with this fixture-style notification probe.

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 states a hard prerequisite ('Subscribe first') and maps that prerequisite to two different transports depending on connection era. It stops short of saying what happens if you call it unsubscribed or when to prefer it over other test tools, but the setup condition is explicit.

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