Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Browser flow (URL-mode elicitation)

elicit_url
Read-only

Opens a local web page for users to enter a fake API token, simulating secret entry that bypasses the model, then confirms the server received it masked.

Instructions

Ask the client to open a local web page where the user enters a fake API token (simulates OAuth / secret entry that must not pass through the client or model). The tool then confirms the server received it (masked).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely useful context beyond that: the interaction happens in a local web page, the secret is deliberately kept out of the client and model, and the confirmation comes back masked. It stops short of stating whether the call blocks, what happens on user cancellation or timeout, or how long it waits.

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, zero wasted words, with the core action front-loaded before the confirmation detail. The parenthetical about OAuth simulation is well placed, though the sentence structure is slightly nested.

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 no output schema and no parameters, the description carries the full burden of return semantics; it partially meets this by stating the server confirms receipt (masked). It omits the failure path — what the tool returns or does if the user closes the page, declines, or the flow times out — which matters for an interactive browser round-trip.

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, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies all configuration is implicit in the flow itself.

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 gives a concrete verb and resource: it opens a local web page for the user to enter a fake API token, then confirms server receipt. This is clearly distinguishable from sibling elicitation tools like elicit_confirm or elicit_wizard, though it never explicitly contrasts itself with them, so differentiating it relies on the reader's inference.

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?

Usage is only implied by the phrase 'simulates OAuth / secret entry that must not pass through the client or model' — an agent can infer this is for testing out-of-band secret capture, but there are no explicit when-to-use or when-not-to-use conditions and no named alternatives among the many sibling elicitation tools.

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