Skip to main content
Glama
Sign In
linkonda-mcp

linkonda-mcp

by Verano-DE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check remaining link allowance

check_quota
Read-only

Check how many short links are live versus your plan's allowance. Use this before a bulk creation to verify you have enough quota, including anonymous usage.

Instructions

Report how many links are live and how many the current plan allows. Without an API key this reports the anonymous allowance. Use it before a bulk create to check for room.

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": "check_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=true, so the description adds value with API key behavior (anonymous allowance without a key) and what the report contains. It goes beyond the annotation without contradicting 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?

The description is two sentences, front-loaded with the main action, and contains no redundant phrasing. Every word contributes to understanding.

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 zero-parameter, read-only tool without an output schema, the description fully covers what it reports (live vs allowed) and when to use it (before bulk creates), including the anonymous allowance nuance. No gaps remain.

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 has zero parameters, which sets a baseline of 4. The description doesn't need to elaborate on parameter semantics, and the reference to API key context is not a parameter.

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 uses the specific verb 'Report' and clearly identifies the resource: link allowance. It explains exactly what is measured (live links vs. plan allowance) and distinguishes it from sibling tools that create, list, update, or delete links.

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 description explicitly advises using the tool before a bulk create to check for room, which is a clear usage context. However, it doesn't mention when-not-to-use or point to alternatives like the top-tier example does.

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