Skip to main content
Glama

new_servers_count_since

Read-onlyIdempotent

Returns how many MCP servers were first published on or after a date, split by namespace type. Example output: {"since":"2026-10-01","count":16045}. Optional argument: date as YYYY-MM-DD, for example "2026-10-01". With no arguments it counts the last 30 days up to the snapshot date. Good for 'How many new MCP servers since October?'.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD, for example "2026-10-01". Optional: empty means the last 30 days up to the snapshot date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / date / default
      Added value: +""
    • addedInput schema / properties / date / description
      Added value: +"Date as YYYY-MM-DD, for example \"2026-10-01\". Optional: empty means the last 30 days up to the snapshot date."
    • addedInput schema / properties / date / examples
      Added value: +[
      +  "2026-10-01"
      +]
    • removedInput schema / required
      Removed value: -[
      -  "date"
      -]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and idempotentHint already covering safety, the description adds useful behavioral context: the default is the last 30 days up to the snapshot date, results are split by namespace type, and an example output is shown. It does not describe edge cases such as future dates or snapshot freshness, but the additions go meaningfully beyond the annotations.

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?

The purpose is front-loaded, followed by the example output, parameter note, default behavior, and use case. It is compact and readable, though the date format is repeated from the schema, which is slightly redundant.

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?

There is no output schema, so the example output helps disclose return shape, and the default window and namespace split are described. For a one-parameter read-only counting tool, this is nearly complete, with only minor gaps around edge cases.

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 schema already documents the optional date parameter, its format, example, and default behavior. The description repeats that information rather than adding new parameter meaning, so the baseline of 3 is appropriate.

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 and resource: it counts MCP servers first published on or after a date, split by namespace type. This is much clearer than a tautology, but it does not explicitly name or contrast with the sibling daily_new_counts, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a clear usage context with the example 'How many new MCP servers since October?' and explains the default no-argument behavior. It does not state when to use a different tool instead, so it lacks explicit exclusions or alternatives.

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