Skip to main content
Glama

tollbooth-sample

by io.github.lonniev

weather_forget_credentials

Delete vaulted credentials for a specific service and npub.

For operator credentials, pass the operator's own npub. For patron credentials, pass the patron's npub. Always requires proof of npub ownership — a deletion is as destructive as a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubYesThe Nostr public key (npub1...) whose credentials to forget.
serviceYesThe credential service to forget.
dpop_tokenYesRaw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL; content:"", created_at within 60s of now, and a random `nonce` tag recommended. Or a cached dpop_token phrase.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / dpop_token / description
      Previous value: -"A kind-27235 Nostr event signed by npub for this tool."New value: +"Raw JSON of a kind-27235 Nostr event signed by npub —\nnot base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its\n`u` tag must hold THIS tool's exact name (from tools/list), not\nthe endpoint URL; content:\"\", created_at within 60s of now, and a\nrandom `nonce` tag recommended. Or a cached dpop_token phrase."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description effectively discloses that the operation is destructive and requires authentication (dpop token). This adds necessary behavioral context beyond the input schema.

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?

Two concise sentences that front-load the core function and then provide usage context. Every sentence adds value without redundancy.

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?

Given the presence of an output schema and detailed parameter schema, the description covers the essential function and usage context. It mentions destructive nature and authentication, though could note what happens on failure or success.

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 description coverage is 100%, and parameter descriptions are detailed (e.g., dpop_token specifies format and constraints). The tool description does not add extra parameter info, meeting the baseline expectation.

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 clearly states the action ('Delete vaulted credentials') and the target resource ('for a specific service and npub'). It distinguishes from sibling tools like weather_delete_coupon and weather_delete_patron_credential by focusing on vaulted credentials.

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?

Provides guidance on when to use operator vs patron npub and emphasizes the requirement for proof of ownership. Does not explicitly list when not to use or name alternatives, but the context is clear.

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

All tollbooth-sample toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed descriptions, and the few similar pairs (e.g., check_balance vs check_authority_balance, account_statement vs account_statement_infographic) are well-differentiated by their descriptions. However, some overlapping concepts like forget_credentials vs delete_patron_credential/delete_operator_credential could still cause misselection without careful reading.

Naming Consistency2/5

All tools share the misleading 'weather_' prefix, which does not reflect their actual domain (billing, credentials, coupons, notarization). Naming patterns are inconsistent, mixing verb_noun (check_balance, list_coupons) with noun-ish names (account_statement, current, forecast) and varied verbs (get, list, check, request, receive, update, delete, forget, mint, redeem, etc.).

Tool Count1/5

With 52 tools, this is an extremely large surface for a sample server. Even though the domain is broad, this count far exceeds the typical well-scoped MCP server and creates unnecessary complexity for agents to navigate.

Completeness4/5

The tollbooth/billing domain is well-covered: credit purchasing, coupons, credentials, proofs, pricing models, notarization, and operator/patron status. Minor gaps exist (e.g., no single-coupon getter, no direct patron list), but core workflows have no dead ends. The weather aspect is thin with only three tools, but that seems intentional as an example paid service.

Resources