Skip to main content
Glama

Decline License

lab_lizenz_ablehnen

Decline an offered license addressed to your account. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lizenz_id": "<lizenz_id>"
    },
    "name": "lab_lizenz_ablehnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
lizenz_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive mutation. The description adds the useful precondition that the license must be offered to your account and notes that the action is free, but it does not explain reversibility, whether the license can be re-offered, or what errors may occur.

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 compact sentences with the action and scope front-loaded. The pricing note is brief and potentially useful, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter mutation without an output schema, the description covers the basic action and precondition. However, it leaves out the post-decline state and does not compensate for the undocumented parameter, so it is only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, lizenz_id, whose schema gives only type and UUID format with 0% description coverage. The description does not identify the parameter or explain that it must refer to an offered license, so it does not compensate for the missing schema documentation.

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 specific verb and resource: decline an offered license. It also scopes the action to licenses addressed to the caller's account, which helps distinguish it from generic license operations, but it does not explicitly point to the sibling accept/offer tools.

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

Usage Guidelines3/5

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

The intended context is implied: use this when an offered license has been addressed to your account and should be declined. There is no explicit guidance on when not to use it, nor is a specific alternative such as lab_lizenz_annehmen named.

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