Skip to main content
Glama

The Bridge

by dev.thebridge
OverviewDiscussionsAdmin

Update Password Policy

update_password_policy
Idempotent

Set the session token lifetimes on the Bridge app: accessTokenTTL and refreshTokenTTL, both in SECONDS. Only the fields you pass are changed. IMPORTANT — despite the name (kept for parity with bridge auth password-policy), this sets token TTLs and NOTHING about passwords: Bridge exposes no password-complexity, rotation or reuse policy on the management API, so if the user asked for password rules, say so instead of calling this. The access token TTL controls how often a client silently refreshes (short is safer, e.g. 900 = 15 minutes); the refresh token TTL controls how long a user stays logged in without re-authenticating (e.g. 2592000 = 30 days). Read the current values with get_auth_config. Before writing app code that consumes this, call get_integration_guide with topic=auth and the framework the app uses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoId of the Bridge app to act on for this call (see list_apps). Omit to use the current app.
accessTokenTTLNoAccess token lifetime in seconds, e.g. 900 (15 minutes).
refreshTokenTTLNoRefresh token lifetime in seconds, e.g. 2592000 (30 days).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already establish that this is a non-read-only, non-destructive, idempotent mutation. The description adds substantial behavioral context beyond that: only passed fields are changed, the name is a legacy misnomer, and the tool deliberately does not expose password complexity, rotation, or reuse settings.

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 dense but well-structured and front-loaded: the actual behavior is stated first, then the name mismatch warning, then operational guidance. Every sentence adds decision-relevant information for an agent, especially given the misleading tool name.

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 a three-parameter mutation tool with no output schema, the description covers behavior, parameter effects, alternatives, and prerequisites sufficiently. An agent has everything needed to decide whether to call this tool and how to interpret the TTL values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaningful semantics beyond field definitions. It explains that both TTLs are in seconds and describes the real-world effect of each: accessTokenTTL governs silent client refresh cadence, while refreshTokenTTL governs how long a user stays logged in.

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?

The description explicitly states the tool sets accessTokenTTL and refreshTokenTTL on a Bridge app, and directly resolves the misleading name by clarifying it does not manage passwords. This makes the tool immediately distinguishable from what an agent might infer from 'update_password_policy' and from sibling config tools.

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?

It gives explicit when-not-to-use guidance: if the user asked for password rules, say so instead of calling this. It also names concrete alternatives for related tasks, telling the agent to read current values with get_auth_config and to consult get_integration_guide for auth integration work.

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

All The Bridge 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