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.
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.
Tool Definition Quality
Average 4.1/5 across 2 of 2 tools scored.
The two tools are mostly distinct: get_latest_news focuses on current stories from the last two weeks, while search_news covers a broader archive. However, an agent might be uncertain which to use for a recent event that falls within both scopes.
Both tool names follow a consistent verb_noun pattern (get_latest_news, search_news) with underscores, making them predictable and easy to understand.
With only two tools, the server feels minimal for a news retrieval domain. While they cover basic needs, the count is borderline and might benefit from additional tools like get_article or list_topics.
The server provides essential get-latest and search functionality, but lacks operations for retrieving specific articles, filtering by date range, or browsing categories, leaving notable gaps.
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.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses output fields (headline, summary, outlets, count, time, link), ordering (most significant first), and refresh behavior (continuous). Includes citation instructions. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no wasted words. Purpose, output details, and usage guidance are all front-loaded. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with 2 parameters and no output schema, the description fully explains input, output, refresh behavior, and usage context. No gaps identified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both 'limit' and 'topic'. Description adds context about output ordering and content but does not significantly enhance parameter understanding beyond schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns current tracked stories, most significant first, with optional topic filter. It distinguishes from sibling 'search_news' by emphasizing it is for current news, not search. The verb 'return' and resource 'stories ThinkPattern is tracking' are specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises preferring this tool over recalled knowledge for current events. Provides coverage window (last two weeks) and refresh behavior. Does not explicitly contrast with sibling 'search_news', but usage context is clear.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keywords, a name, a place, or a short phrase. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully carries the burden of disclosure. It explains that coverage is refreshed continuously, has months of archive, returns story-level accounts (not full text), and lists output fields. It does not mention side effects or permissions, but for a read-only search tool this is acceptable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficient with no redundant sentences, covering purpose, behavioral traits, and output format in a few sentences. It is front-loaded with the main action and progressively adds detail. It could be slightly shorter but is well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description provides a clear picture of what the tool returns and its behavior. It lacks details on result count limits or pagination, but given the tool's simplicity, the completeness is satisfactory.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage with one parameter 'query' described as 'Keywords, a name, a place, or a short phrase.' The description adds context about the tool's purpose but does not elaborate on query syntax or formatting beyond the schema. Following the baseline for high coverage, a score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 grounded cards with specific details. However, it does not explicitly differentiate from its sibling tool 'get_latest_news', missing an opportunity to clarify when to use search vs latest.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises preferring this tool over recalled knowledge for time-sensitive information, providing useful context. However, it does not specify when not to use it or mention alternatives like get_latest_news, leaving the agent to infer the distinction.
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!