Skip to main content
Glama

RenewRoster

List tracked assets

list_assets
Read-onlyIdempotent

All tracked domains and SSL certificates with filters.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
clientNoclient id, or 'none' for unassigned
offsetNo
statusNo
expiring_withinNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond that: it doesn't mention the default page size (limit max 1000), pagination via offset, or what fields a returned asset carries, which matters for an unbounded default (required params: 0).

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

Conciseness3/5

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

The single sentence is front-loaded and wastes nothing, but it is a terse fragment rather than a structured definition. Shortness here reflects under-specification more than good editing.

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

Completeness2/5

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

Six optional parameters, no output schema, and 17% schema coverage demand more than seven words. An agent still cannot tell the default page size, the units of expiring_within, or the shape of an 'asset' in the response.

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?

Schema description coverage is only 17% — just the 'client' parameter (including the 'none' sentinel) is documented; type, status, limit, offset and expiring_within carry no meaning in either schema or description. Critically, expiring_within's unit (days?) and the default limit are never stated, so the description fails to compensate for the coverage gap.

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?

Names the resource precisely ('all tracked domains and SSL certificates') and implies the list operation, which distinguishes it from the singular get_asset and from the narrower list_expiring. It does not explicitly contrast itself with those siblings, which keeps it below a 5.

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?

No statement of when to use this versus list_expiring, list_clients, get_asset, or lookup_domain, all of which overlap in scope. The reader must infer that this is the unfiltered enumeration and that expiring-specific queries belong elsewhere.

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.