Skip to main content
Glama

RenewRoster

Get one asset

get_asset
Read-onlyIdempotent

One tracked domain or certificate by id, with recent check history.

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": {
      "id": "<id>"
    },
    "name": "get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds only that the response includes recent check history; it says nothing about behavior when the id does not exist, how much history is included, or whether the lookup is cacheable.

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?

One compact clause with zero padding, and the key content (single asset by id, plus history) is front-loaded. It is a sentence fragment rather than a complete statement, which slightly hurts readability but wastes no words.

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?

With no output schema, the description must carry return-value information, and it does at a high level by stating the response contains recent check history alongside the asset. For a one-parameter read-only lookup with full annotation coverage, nothing essential to correct invocation is missing beyond edge-case behavior.

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 should compensate, and 'by id' only mildly does: it confirms the parameter selects a single asset but not whether the id is a numeric asset id, a domain name, or a certificate serial (minLength/maxLength=64 hints at an opaque string). With a single obvious parameter, baseline 3 is defensible but the format ambiguity is a real 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 a specific verb (get) and resource (one tracked domain or certificate) with scope 'by id', plus a note on payload contents (recent check history). This separates it from list_assets, but it does not explicitly distinguish it from the near-identical sibling get_asset_history, which likely supplies the same history at greater depth.

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 phrase 'by id' implies the usage (single-item lookup when an identifier is known) versus the list_* siblings, but no when/when-not guidance or named alternative is given. An agent must infer that get_asset_history or lookup_domain/lookup_cert are the alternatives for deeper history or name-based lookup.

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.