Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Get my subscription

subscription_get
Read-onlyIdempotent

Purpose: Read the user's searchnapply subscription, its daily call limit and what was used today; a value that is unknown is left out. When: The user asks about their subscription, or why a tool stopped answering. Cost: About 50 tokens.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYesThe plan as Billing reports it.
usageYesToday's usage.
limitsNoThe plan's limits; absent when Billing did not answer.
statusYesThe subscription status as Billing reports it.
renewsAtNoThe date the plan renews; present only when it renews.
trialEndsAtNoWhen the introductory period ends, if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / trialEndsAt / description
      Previous value: -"The date the trial ends; present only on a trial."New value: +"When the introductory period ends, if any."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered by structured data. The description adds one genuinely new behavioral fact – that unknown values are omitted from the result – and a rough cost figure, but nothing about failure modes or what happens when no subscription exists.

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) put the essential information first with no filler. The cost note is short and plausibly useful for an agent managing context budget.

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?

An output schema exists, so return values need not be re-explained, and the omission-of-unknown-values note fills the one gap that schema does not convey. Minor residual gap: no mention of what the result looks like when the user has no subscription at all.

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 the baseline is 4 and there is no parameter meaning left to add. The description correctly adds no invented parameter guidance.

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?

States a specific verb and resource (read the user's searchnapply subscription) plus the concrete fields returned (daily call limit, usage today). The scope is unambiguous and clearly distinct from the sibling subscription_links, which handles links rather than subscription state.

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 two concrete triggers: the user asks about their subscription, or a tool stopped answering due to quota. It does not explicitly name subscription_links as the alternative for link-related questions, so routing between the two still needs inference from the names.

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