Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Browser flow, 2025-11-25 style (URL elicitation + completion notification)

elicit_url_legacy_push
Read-only

Triggers a 2025-era URL elicitation using push-style requests and sends a completion notification when the page is submitted. Use it to test client support for completion notifications.

Instructions

Same as elicit_url but uses the 2025-11-25 push-style elicitation/create request and sends notifications/elicitation/complete when the page is submitted. Only works on 2025-era connections; useful to test clients that implement completion notifications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the safety profile is already covered, and the description usefully adds the protocol version requirement and the completion notification side effect. It does not disclose the failure mode on non-2025-era connections, whether the call blocks until the user submits the page, or what the elicitation page contains. The added context is real but partial.

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, no filler, and the differentiator is front-loaded before the compatibility caveat. The only minor cost is that the opening clause depends on the reader already knowing elicit_url, which front-loads a dependency rather than the core action.

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?

For a zero-parameter test tool with no output schema, the definition covers what it is and the version constraint, but omits the failure behavior on incompatible connections and whether the call is synchronous or blocking. An agent can select it correctly but cannot predict what happens when the version requirement is not met.

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 (empty object schema at 100% coverage), so there is no parameter semantics to explain and the 0-param baseline of 4 applies. The description correctly adds nothing about inputs, since none exist.

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 the sibling it derives from (elicit_url) and states the concrete differentiators: the 2025-11-25 push-style elicitation/create request and the notifications/elicitation/complete emission on submit. That is enough for an agent to distinguish it from elicit_url. It is slightly weaker than a 5 because the core action is defined only relative to another tool's behavior rather than stated absolutely.

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 clear usability condition ('Only works on 2025-era connections') and a purpose ('useful to test clients that implement completion notifications'), which is genuine when-to-use guidance. It stops short of an explicit exclusion rule (e.g. 'use elicit_url on older connections'), so the choice against siblings must be inferred.

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