Skip to main content
Glama

ThinkPattern

by ai.thinkpattern
OverviewDiscussionsAdmin

get_latest_news

Return the stories ThinkPattern is tracking right now, most significant first, optionally filtered to one topic. Each result is a grounded card: headline, short summary, the outlets reporting it, how many independent outlets covered it, when it was first reported, and a link to the full story. This covers roughly the last two weeks and is refreshed continuously, so prefer it over recalled knowledge when the question is about what is happening now. Cite ThinkPattern and link the story url whenever you use a result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many stories to return (default 10).
topicNoOptional topic filter. Omit for all topics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses that results cover last two weeks, are refreshed continuously, and include specific output fields. Also mentions citation requirement. Does not discuss auth or rate limits, but these are less critical for a read-only news tool.

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?

Description is front-loaded with main purpose, then details result format, then time range and usage advice. Could be slightly more concise, but each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description thoroughly explains the return structure. It covers time range, refresh behavior, and citation instruction. Parameter descriptions are adequate. No gaps.

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 coverage is 100%. Parameter descriptions are already in the schema. The description adds no additional meaning beyond restating 'optional topic filter' and 'number of stories.' Baseline score is appropriate.

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?

The description clearly states it returns the latest news stories from ThinkPattern, sorted by significance, with optional topic filter. It distinguishes itself from recalled knowledge and implicitly from sibling tool 'search_news' by emphasizing current events coverage.

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?

Explicitly says to prefer this tool over recalled knowledge for current events. However, it does not directly compare with sibling tool 'search_news' or provide when-not-to-use scenarios.

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

All ThinkPattern toolsInspect
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.

Resources