Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Get my plan's site links

subscription_links
Read-onlyIdempotent

Purpose: Give the two site pages where the plans and the account are described; calls nothing. When: The user asks where the plans or the account page are. Cost: Under 30 tokens for the reply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "subscription_links"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
portalUrlYesThe account page where the user manages the plan.
pricingUrlYesThe plans page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / portalUrl / description
      Previous value: -"The account page, where the user opens the billing portal to change or cancel the plan."New value: +"The account page where the user manages the plan."
    • changedOutput schema / properties / pricingUrl / description
      Previous value: -"The pricing page, where the plans and their prices are."New value: +"The plans page."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds two things annotations cannot: 'calls nothing' (no downstream dependency or side effect) and a token-cost bound on the reply, which helps an agent decide whether to spend a call on it.

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?

Three labeled lines (Purpose / When / Cost), front-loaded with the verb and resource and with zero filler. Every line carries distinct information; nothing repeats the title or annotations verbatim.

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?

An output schema exists, so return values need not be described, and there are no parameters to explain. For a trivial two-URL lookup, the definition supplies everything needed to decide and invoke correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a parameterless tool applies. Nothing in the description contradicts or is needed beyond the empty schema.

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?

States a concrete verb and resource: returns the two site pages describing plans and the account. An agent can distinguish it from subscription_get (which presumably returns plan data rather than page URLs), though the sibling is never named explicitly.

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?

The 'When' line gives an explicit trigger: the user asks where the plans or account page are. It does not state when to prefer a sibling such as subscription_get instead, but the trigger is clear enough that misfire risk is low.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources