There's An AI For That

Get breakthrough details

get_breakthrough

Read-only

Get one public AI breakthrough by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_breakthrough"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The numeric ID returned by search_breakthroughs.

Output Schema

Name	Required	Description	Default
`error`	No
`breakthrough`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026
- addedOutput schema / properties / breakthrough / properties / downvotes / description
```
Added value: +"Number of TAAFT downvotes for this news item."
```
- addedOutput schema / properties / breakthrough / properties / popularity / description
```
Added value: +"Net TAAFT news votes: upvotes minus downvotes."
```
- addedOutput schema / properties / breakthrough / properties / upvotes / description
```
Added value: +"Number of TAAFT upvotes for this news item."
```
AddedOct 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the constraint that only 'public' breakthroughs are retrievable, which is genuinely new context, but says nothing about behavior for invalid or private IDs.

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 sentence with the verb and scope front-loaded and zero wasted words. Nothing in it is redundant with the title or padding.

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?

An output schema exists, so return values need no explanation, and the sole parameter is well documented. However, for a getter the description omits anything about failure modes or what 'public' excludes, leaving it merely adequate.

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 the single 'id' parameter is fully documented in the schema, including its minimum and its origin from search_breakthroughs. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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 ('Get one public AI breakthrough') and scopes it to a single record by ID, which separates it from search_breakthroughs. It stops short of explicitly naming the sibling search tool, but the singular 'one ... by ID' framing makes the distinction inferable.

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?

The description offers no when-to-use or when-not-to-use guidance. The lookup flow is only hinted at in the schema ('returned by search_breakthroughs'), so an agent reading just the description gets no routing advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All There's An AI For That tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.