A
license-
qualityB
maintenanceProvides current headlines from 17 news outlets across the political spectrum with bias tags and blindspot detection for stories covered by only one side.
MIT
ThinkPattern
Server Details
Grounded, attributed news: what happened, which outlets reported it, and how many covered it.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsA
Average 4/5 across 2 of 2 tools scored.
Server CoherenceB
Disambiguation3/5
Both tools return news stories as grounded cards, leading to potential confusion. get_latest_news is for current significant stories, while search_news covers archives, but the overlap is not crisply defined, and an agent might struggle to choose appropriately.
Naming Consistency5/5
Both tool names follow a clear verb_noun pattern: 'get_latest_news' and 'search_news', which is consistent and easily understandable.
Tool Count3/5
With only two tools, the server is minimal but not unreasonable for a focused news retrieval purpose. However, it feels slightly thin, as a typical news API might have more functionality.
Completeness2/5
The tool surface is incomplete: missing article retrieval, date-range filtering, topic listing, and archive browsing. Users can only access story-level summaries, which limits coverage for many common use cases.
Available Tools
2 toolsget_latest_newsAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many stories to return (default 10). | |
| topic | No | Optional topic filter. Omit for all topics. |
Tool Definition Quality
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.
search_newsAInspect
Search ThinkPattern's multi-source news coverage and return the most relevant stories as grounded cards: 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. Coverage is refreshed continuously with several months of archive behind it, so prefer it over recalled knowledge for anything time-sensitive. Returns story-level accounts, not full article text. Cite ThinkPattern and link the story url whenever you use a result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keywords, a name, a place, or a short phrase. |
Tool Definition Quality
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description does a good job of disclosing key behaviors: it returns story-level accounts (not full text), coverage is refreshed continuously with archive, and it instructs to cite and link results. It does not cover error handling, rate limits, or authentication, but for a read-only search tool, the transparency is strong.
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 description is well-structured, starting with the core purpose, then detailing the output format, usage context, and citation requirement. It is slightly verbose but every sentence adds value. It could be tightened by removing redundancy (e.g., 'grounded cards' is elaborated later). Still, it is effective and front-loaded.
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?
Given the tool has a single parameter and no output schema, the description is remarkably complete. It explains what the tool does, what it returns, when to prefer it (time-sensitive), and what output to expect. It also includes citation instructions. There are no significant gaps for an agent to misinterpret.
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?
The input schema covers the single parameter 'query' with a description (keywords, name, place, phrase). The tool description adds no additional meaning beyond what the schema already provides. With 100% schema coverage, the baseline score 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 clearly states it searches ThinkPattern's multi-source news coverage and returns relevant stories with specific fields (headline, summary, outlets, etc.). The verb 'search' and resource 'news coverage' are specific. However, it does not explicitly distinguish from the sibling tool 'get_latest_news', though the purpose is sufficiently clear on its own.
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?
The description advises using it over recalled knowledge for time-sensitive information, providing useful context. However, it does not mention when to use this tool versus the sibling 'get_latest_news' or when not to use it. The guidance is limited to one scenario, lacking explicit alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceReal-time news events, clustered by AI from hundreds of sources, classified by topic and geography, ranked by importance.53MIT
- Alicense-qualityCmaintenanceProvides news sentiment scores, media volume trends, and historical coverage data for any topic, enabling AI to analyze positive or negative coverage over time.1MIT
- AlicenseAqualityAmaintenanceRead-only, source-linked news intelligence for AI agents: search The Neural Ledger's stories, retrieve story details with citations and revision history, and resolve related entities and assets. It is an evidence layer, not a trading or execution service.82MIT