Skip to main content
Glama

Panel: read an open ask

secret_request
Read-only

Fetches the pending request form using its request_id so the app UI can render open asks when host-provided _meta is absent. App-only; never exposed to the model.

Instructions

The panel reads the form for an open ask (its request_id, in the visible result) when the host didn't hand it the result's _meta. App-only: the model never sees this tool or its result.

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": {
      "request_id": "<request_id>"
    },
    "name": "secret_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false; the description adds genuinely new context, namely that this is a host-side panel call whose result is invisible to the model. It does not say what happens on an unknown or already-consumed request_id, nor whether the call has side effects on the ask's state.

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 immediately followed by the trigger condition and the visibility constraint. Dense but every clause carries information; no filler.

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 single-parameter read-only panel tool with no output schema and full annotation coverage, the description supplies the trigger, the parameter source, and the visibility rules. Only edge-case behavior (invalid or stale request_id) is left uncovered.

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 0%, so the description must carry the parameter, and it does: request_id is described as coming from "the visible result" obtained elsewhere. That sourcing guidance is real value beyond the bare string schema, though the expected format or failure behavior is still unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ("reads the form for an open ask") and names the key payload (request_id), but "open ask," "the form," and "the panel" are unexplained domain jargon. It is distinguishable from siblings only because it declares itself app-only, not because the purpose is described in plain terms.

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?

Gives an explicit invocation condition: use it "when the host didn't hand it the result's _meta." It also states a hard exclusion (app-only, the model never sees this tool or its result). What is missing is any named alternative for the case where _meta was supplied.

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