Skip to main content
Glama

AIML Rounds

What's new

whats_new
Read-only

Lessons, designs, quizzes and mock rounds added to the site recently, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely behavioral fact not in annotations — results are ordered newest first — but says nothing about pagination, whether the limit caps the feed, or how many content types are interleaved.

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 short sentence, front-loaded with the content types and ending with the ordering rule; nothing is padded or redundant. The trade-off is that brevity here shades into under-specification rather than tightness.

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 read-only feed with one optional parameter and no output schema, the definition covers what the tool returns at a high level. It still leaves gaps an agent would want filled: what a single item looks like, whether the limit is total or per content type, and how to page deeper into the feed.

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 0% and the single parameter (limit, default 15, max 60) is never mentioned in the description. The schema's name, default and range make the parameter largely self-explanatory, but the description contributes no meaning about what the limit counts or how truncation is signaled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely (lessons, designs, quizzes, mock rounds added recently) and its ordering (newest first), so an agent knows what content comes back. But it is a bare noun phrase with no verb and no differentiation from siblings like browse or search, leaving the agent to infer that this is a 'list recent additions' feed.

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?

There is no when-to-use or when-not-to-use guidance. The description never contrasts this recent-additions feed with browse (browse the catalog) or search (query by term), which are the obvious alternatives for an agent wanting content.

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