Skip to main content
Glama

Today's specials

todays_specials
Read-only

Live security incidents right now (CVEs, breaches, supply-chain compromises) with severity, patch status, fixed versions and ids. Pass stack ids to see only what touches your stack. Known ids: nextjs, react, node, bun, php, python, ruby, go, java, wordpress, drupal, magento, perl, proof-tools, dotnet, rust, npm, pypi, github-actions, docker, vscode, browser-ext, linux, linux-services, openssh, nginx, apache, kubernetes, postgres, mysql, redis, gitlab, ci, atlassian, self-hosted, selfhost-apps, paas, cloudflare, aws, gcp, azure, vps, databases-cloud, ai-gateways, ai-keys, ml-infra, mcp, chrome, apple, android, windows, office, office-suites, password-managers, messaging, crypto-wallets, vpn-edge, ics, remote-support, vmware, security-tools, health-it, erp.

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

Input Schema

NameRequiredDescriptionDefault
stackNoStack ids to filter by, e.g. ["nextjs","npm"]. Omit for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 genuinely useful behavioral detail by enumerating the returned fields (severity, patch status, fixed versions, ids) in the absence of an output schema. It does not say what happens with an unrecognized stack id, how fresh the feed is, or whether results are paginated/limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and filtering rule are correctly front-loaded in the first two sentences. The remaining bulk is a ~60-item id dump that earns most of its place (no enum in the schema) but is unstructured and could be grouped by category for faster scanning.

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 one-optional-parameter read tool with no output schema, the definition covers returned fields, the filter vocabulary, and the no-filter default. Remaining gaps are secondary: label scale for severity, staleness/caching of a 'live' feed, and invalid-id handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single optional 'stack' array, so the baseline would be 3. The description exceeds that by supplying the actual valid id vocabulary (nextjs, npm, kubernetes, aws, ...) that the schema does not encode as an enum, plus the 'omit for everything' default. It loses a point for dumping the ids as an ungrouped wall with no indication of what an invalid id does.

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 names a specific resource and scope: live security incidents (CVEs, breaches, supply-chain compromises) with severity, patch status, fixed versions and ids. An agent immediately knows this is a current-incident feed rather than a per-CVE lookup or a changelog, which implicitly separates it from lookup_cve and whats_new. It stops short of explicitly naming those siblings as alternatives, so no 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?

'Live ... right now' and 'Omit for everything' imply when the tool is appropriate and what the default behavior is. However, there is no explicit when-not guidance and no mention of when to prefer lookup_cve or whats_new instead, leaving the routing decision to inference.

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