Skip to main content
Glama

What changed in the data

whats_new
Read-onlyIdempotent

Use when the user asks what is new or what changed recently in AI startup revenue figures. Returns the change log, newest first: businesses added and figures added, revised, re-dated or removed, each with source_url; filters since (YYYY-MM-DD), slug, kind, limit (max 100). Example: {"since":"2026-10-14"} -> every change since Oct 14, 2026. Cost: free (100 calls/day without a key).

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
kindNoOnly this kind of change: dataset_created, business_added, business_removed, metric_added, metric_revised, metric_redated, metric_removed. Omit for all kinds.
slugNoOnly changes for this business slug, e.g. cursor (slugs come from search_businesses or leaderboard).
limitNoDefault 20, max 100.
sinceNoOnly changes on or after this date, YYYY-MM-DD (e.g. 2026-10-14).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"Only this kind of change: dataset_created, business_added, business_removed, metric_added, metric_revised, metric_redated, metric_removed. Omit for all kinds."
    • changedInput schema / properties / since / description
      Previous value: -"YYYY-MM-DD"New value: +"Only changes on or after this date, YYYY-MM-DD (e.g. 2026-10-14)."
    • addedInput schema / properties / slug / description
      Added value: +"Only changes for this business slug, e.g. cursor (slugs come from search_businesses or leaderboard)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds context annotations can't: newest-first ordering, the entry contents (businesses added, figures added/revised/re-dated/removed), per-entry source_url, and a cost/rate-limit note ('free, 100 calls/day without a key'). It does not mention pagination or what a key unlocks, keeping it short of a 5.

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?

Front-loaded with the use case, then return shape, then filters, then an example, then cost — every sentence carries distinct information and there is no filler or repetition.

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?

An output schema exists, so the description needn't fully specify return values, yet it still sketches the payload and ordering. Usage, cost and filtering are all covered; only pagination/truncation behavior at limit 100 is left implicit.

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 all four params are already documented (kind enum, slug source, limit max, since date format). The description restates the filters and adds a worked example ('{"since":"2026-10-14"}'), which is helpful but largely redundant — baseline 3 applies.

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

Purpose5/5

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

States a specific trigger and resource: 'what is new or what changed recently in AI startup revenue figures', and names the return payload as a change log. No sibling tool (leaderboard, get_business, search_businesses) covers a change feed, so the agent can route without opening the schema.

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?

Gives an explicit trigger condition ('when the user asks what is new or what changed recently') and a concrete example call. It doesn't state exclusions or when to prefer a sibling, but the trigger is unambiguous enough for correct selection.

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