Skip to main content
Glama

WEIR AI

List my licenses

list_licenses
Read-onlyIdempotent

List licenses the connected WEIR AI account owns or manages (including roster clients the account is permitted to see). Use for 'my licenses' or as the first step of monitoring. Optional page, per_page 1-100. Needs a connected WEIR AI account with license:read; if it returns AUTHENTICATION_REQUIRED, tell the user WEIR AI needs account authorization through their assistant's connection settings. [Needs a connected WEIR AI account; scope license:read]

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

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely new operational context: the license:read scope requirement and, importantly, the remediation path when AUTHENTICATION_REQUIRED is returned (tell the user to authorize via their assistant's connection settings) — that is behavior an agent cannot infer from structured fields.

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?

Front-loaded with purpose, then usage, then parameters, then the auth/error path — a sensible descending priority. The trailing bracketed '[Needs a connected WEIR AI account; scope license:read]' restates the auth requirement already given a sentence earlier, which is avoidable duplication.

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?

For a read-only, two-optional-parameter list tool with no output schema, the description covers purpose, scope, usage, pagination, auth scope, and the failure path. The remaining gap is that it never hints at what a returned license record contains, which an agent enumerating licenses for monitoring would want.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden. It names both parameters, marks them optional, and states 'per_page 1-100' — but the range and defaults are already in the schema (maximum 100, default 20, default page 1), so the added meaning is thin. It does not say what ordering the page window follows, which would matter for monitoring.

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?

Names a specific verb and resource ('List licenses') and pins down scope precisely: licenses the connected WEIR AI account 'owns or manages (including roster clients the account is permitted to see)'. That scope sentence is what separates it from get_license, get_public_license, and search_catalog, which an agent can resolve without opening any schema.

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?

'Use for "my licenses" or as the first step of monitoring' gives a concrete triggering intent and a sequencing role relative to other tools. It stops short of naming when NOT to use it or pointing to get_license for a single record, so it does not reach a full 5.

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