Skip to main content
Glama

User Intuition

by ai.userintuition
OverviewDiscussionsAdmin

Delete External Panel Configuration

delete_external_panel
Destructive

Disable the external-panel entry link for an owned BYOP study. Existing interviews remain; the provider can no longer send new respondents through this link. A repeated deletion returns 404.

Input Schema

NameRequiredDescriptionDefault
study_idYes
organization_idNoOrganization for this operation and billing. Use list_organizations to choose an active membership.

Output Schema

NameRequiredDescriptionDefault
resultYesExternal-panel configuration disabled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / organization_id / description
      Previous value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."
  2. Changed1 schema field changed
    • addedInput schema / properties / organization_id
      Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructive and non-idempotent annotations, the description clarifies exactly what is affected: existing interviews remain, the provider can no longer send new respondents through the link, and repeated deletion returns 404. This is high-value behavioral detail for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with the core effect front-loaded. Each sentence adds relevant information: purpose, preservation of existing interviews, and repeated-deletion behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the destructive annotations, partial schema descriptions, output schema, and sibling tools, the description provides enough context to invoke the tool correctly. It covers the critical side effects and repeated-call behavior without needing to explain return values.

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 coverage is 50%, with organization_id documented in the schema and study_id documented only by type/pattern. The description adds the useful constraint that the study must be an owned BYOP study, but it does not explain organization_id or add further detail about study_id beyond that constraint.

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 states a specific action and resource: disabling the external-panel entry link for an owned BYOP study. It clearly conveys the operational effect, but it does not explicitly distinguish the tool from close siblings such as configure_external_panel, get_external_panel, or regenerate_external_panel_token.

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?

The description gives implied usage context by saying it applies to an owned BYOP study and leaves existing interviews intact while preventing new respondents from using the link. It does not explicitly state when to use this instead of related tools such as regenerate_external_panel_token or configure_external_panel.

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

All User Intuition 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