Skip to main content
Glama

vspc_get_console_license

Read-onlyIdempotent

Retrieve the VSPC console license details—edition, package, status, expiry, support expiry, and last update result—to verify licensing and track renewal or support deadlines.

Instructions

The VSPC console license: edition, package, status, expiry and support expiry, last update result.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a safe, idempotent, read-only, open-world read. The description's added value is modest but real: it tells the agent that 'last update result' is included, hinting at a freshness/health signal. It says nothing about whether the license is queried live from a server or cached, nor about failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact fragment with zero filler, front-loading the resource and then listing the returned fields. It is a sentence fragment rather than a complete sentence, but every word earns its place.

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?

With no parameters and no output schema, the description carries the burden of describing what comes back, and it does so by enumerating the returned fields. For a simple read-only getter this is close to sufficient; only the ambiguous boundary with the license-usage sibling is unaddressed.

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 input schema has nothing to document and the baseline is 4. No parameter explanation is required or expected here.

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?

The description names a specific resource (the VSPC console license) and enumerates the exact fields it reports: edition, package, status, expiry, support expiry, and last update result. This is substantially more informative than the bare tool name, though it omits the verb and does not distinguish itself from the similarly named sibling vspc_get_license_usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this tool, no mention of prerequisites, and no explicit contrast with siblings such as vspc_get_license_usage. The only implicit signal is that it concerns the console license rather than usage metrics, leaving the agent to infer the use case.

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