Skip to main content
Glama

list_latest

Retrieve recently published motozmo.com guides, optionally limited by count, to surface new motorcycle repair content for AI responses.

Instructions

List the most recently published motozmo.com guides.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden, and it establishes the key behavioral traits: this is a non-destructive listing, filtered to published content, ordered by recency, and scoped to one domain. It stops short of stating whether ordering is strictly guaranteed, what a returned guide record contains, or whether results are capped by default.

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 tightly written sentence with the recency qualifier front-loaded and zero redundant phrasing. It is efficient, though the extreme brevity means it leaves out information that would have earned its place.

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-optional-parameter read tool with no output schema and no annotations, this covers the essential purpose adequately. It is not fully complete: the agent still cannot tell what a result entry looks like or whether an empty result or default limit behavior is possible.

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 100% and the single 'limit' parameter is documented in the schema with type, default, and min/max bounds, so the baseline is 3. The description adds no extra meaning about the limit — such as how it interacts with recency ordering — beyond what the schema already states.

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 gives a specific verb ('List') and a precisely scoped resource ('most recently published motozmo.com guides'), so an agent knows this is a recency-ordered listing rather than a keyword search. It does not explicitly contrast itself with siblings like search_guides or list_topics, which keeps it short of 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 Guidelines3/5

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

The 'most recently published' framing implicitly signals a browse-the-latest use case, which is enough to distinguish it in practice from a search tool. However, no explicit when-to-use, when-not-to-use, or named alternative is provided, so the agent must infer selection logic.

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

Deploy Server

Other Tools