Skip to main content
Glama
vienneje

foodpanda-mcp

by vienneje
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Refresh Session Token

refresh_token

Renews expired foodpanda session tokens by opening a login window and automatically capturing the new session after manual authentication.

Instructions

Opens a browser window to https://www.foodpanda.hk so the user can log in to their foodpanda Hong Kong account. Intercepts the session token from network requests and updates the server. Call this when: (1) other tools return a 'session token expired' or 'No session token configured' error, or (2) the user wants to switch accounts. The browser window is visible — the user logs in manually (handling any CAPTCHAs or MFA). Once logged in, the token is captured automatically and saved for future sessions. Requires a desktop session; on a headless server set FOODPANDA_HEADLESS=1 and expect to complete the login elsewhere.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNoHow long to wait for login in seconds (default 120). Increase if the user needs more time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, so description fully discloses interactive login, manual user action, CAPTCHA/MFA handling, automatic token capture, desktop requirement, and headless alternative. No contradictions.

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?

Well-structured with numbered triggers and a clear sequence, but slightly verbose. Every sentence adds value though; front-loads the trigger conditions before procedural details.

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?

For an interactive auth tool with no output schema, it covers prerequisites, side effects, error conditions, and environment constraints. Nothing essential 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?

Schema already documents timeout with default and purpose. Description adds practical guidance ('Increase if the user needs more time'), going slightly beyond the schema's description.

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?

Clearly states it opens a browser window, intercepts the session token, and updates the server. Distinct from sibling tools (all foodpanda operations) by focusing on authentication.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists two conditions for invocation: session token expired/not configured errors, or user wants to switch accounts. Also provides headless server guidance.

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

Deploy Server

Other Tools