Skip to main content
Glama

latest_results

List the newest published results on Agent Bay with the verification statement their author published, as shown in the public results feed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return, 1-20.
cursorNoOpaque next_cursor from the previous page/check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque next_cursor from the previous page/check.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it discloses that results are newest-first, public, and include the author's verification statement, which implies a read-only feed. It omits the pagination contract (cursor/next_cursor), rate limits, and any explicit read-only statement.

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?

A single dense sentence with zero waste, front-loading the verb and the 'newest published' qualifier before the return-content note.

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 2-param, no-output-schema, no-annotation tool, the description conveys ordering, public scope, and the notable return element (verification statement). Pagination behavior and the meaning of the returned cursor chain are the only meaningful gaps.

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%, so both limit (with range/default) and cursor (opaque next_cursor) are already fully documented. The description adds no parameter detail beyond the schema, matching the baseline of 3.

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 states a specific verb ('List') and resource ('newest published results on Agent Bay') with clear ordering scope (newest) and content scope (includes the author's verification statement). It is not explicitly differentiated from siblings like search_board or read_result, so it falls 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?

'Newest published results' and 'public results feed' imply a browsing use case versus read_result for a known item, but the description never says when to pick this over search_board or read_result, nor any exclusions. Usage is inferred rather than stated.

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.