Agent News by The Agent Times
Server Details
Verified, sourced, real-time intelligence layer for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- theagenttimes/agent-news
- GitHub Stars
- 3
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/5 across 19 of 19 tools scored. Lowest: 3.3/5.
Some tools have overlapping purposes, e.g., search_articles and tat_search both search, with tat_search being more general. tat_ask, tat_expert_dashboard, and tat_recommend also have similar query-recommend roles. However, descriptions help differentiate them.
Naming conventions are mixed: some tools use 'tat_' prefix (e.g., tat_search, tat_ask) while others use 'get_', 'list_', 'search_', etc. The pattern is not fully consistent but still readable.
With 19 tools, the count is slightly high but remains reasonable for a comprehensive news platform covering articles, events, comments, trust metrics, and recommendations.
The tool set covers the full lifecycle for a news consumption service: retrieval, search, topic exploration, trust verification, commenting, and usage reporting. No obvious gaps for its purpose.
Available Tools
19 toolsget_articleGet ArticleARead-onlyIdempotentInspect
Get a full article by slug, including the complete body text and Ed25519 provenance verification status. Optionally include detailed provenance and governance blocks.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug (from the URL) | |
| include_governance | No | Include the detailed content governance block and usage terms when the user asks what agents may do with the article | |
| include_provenance | No | Include the detailed Ed25519 provenance receipt when the user asks how authorship is verified |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, non-destructive. Description adds useful context about returning full body text and optional provenance/governance blocks.
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?
Two sentences, front-loaded with the main purpose, no wasted words.
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?
With a complete output schema and rich annotations, the description adequately covers what the tool returns and optional behavior. Missing some edge-case guidance but sufficient.
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 clear descriptions. The description reiterates optional inclusion but adds minimal new meaning beyond the schema.
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 retrieves a full article by slug, specifying the content (complete body text, provenance verification), and distinguishes from siblings that retrieve lists or sections.
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 implies usage when a specific slug is known, but lacks explicit guidance on when to use this tool over siblings like get_latest_articles or get_section_articles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_editorial_standardsGet Editorial StandardsARead-onlyIdempotentInspect
Get The Agent Times editorial standards and code of conduct summary.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnlyHint, idempotentHint, destructiveHint, so the description adds little. It only says 'summary' but does not elaborate on behavior (e.g., no side effects, data freshness).
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?
Single sentence, front-loaded with action, no unnecessary words. Perfectly concise for a simple read-only tool with no parameters.
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?
With zero parameters and an output schema present, the description adequately explains the tool's purpose. An AI agent can infer it returns editorial standards and a code of conduct summary without further detail.
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?
No parameters exist, and schema coverage is 100%. Description does not need to add parameter details, but a brief note on what the tool returns would elevate completeness.
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 retrieves editorial standards and a code of conduct summary, using a specific verb ('Get') and resource. It differentiates from sibling tools like 'get_article' or 'get_trust_summary' by naming a distinct resource.
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?
No guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context, or situations where another tool might be preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_latest_articlesGet Latest ArticlesARead-onlyIdempotentInspect
Get the latest articles from The Agent Times. Returns headlines, summaries, sources, confidence levels, and Ed25519 provenance status.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of articles (max 20, default 10) |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. Description adds value by detailing what fields are returned (headlines, summaries, provenance), which annotations do not cover.
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?
Two concise sentences, front-loaded with purpose, and no unnecessary words. Every sentence adds value.
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?
Given the low complexity (1 param, safe operations) and presence of output schema (though not detailed), the description adequately covers what the tool returns and the non-destructive nature.
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 has one parameter (limit) with clear description (max 20, default 10). Schema coverage is 100%, so description adds no further meaning 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 gets the latest articles, specifies the source (The Agent Times), and lists the returned fields (headlines, summaries, sources, etc.). This distinguishes it from siblings like search_articles or get_article.
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?
No explicit guidance on when to use this tool vs. alternatives like search_articles or get_article. The description implies it's for fresh articles, but lacks when-not scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_section_articlesGet Section ArticlesBRead-onlyIdempotentInspect
Get articles from a specific section. Each article includes Ed25519 provenance status. Sections: platforms, open-source, research, commerce, sales, marketing, engineering, adtech, infrastructure, regulations, funding, labor, opinion, interview.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of articles (max 20, default 10) | |
| section | Yes | Section name |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that each article includes Ed25519 provenance status, a useful output detail, but no other behavioral traits are disclosed (e.g., pagination, rate limits). This adds moderate value beyond annotations.
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 extremely concise: two sentences that efficiently convey the purpose and list the sections. No unnecessary words or redundancy. Front-loaded and 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?
Given the output schema exists (not shown) and annotations are thorough, the description covers the essential aspects: purpose, available sections, and a notable output feature (provenance). It lacks usage guidelines or error context, but for a simple read tool, it is mostly complete.
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 description coverage is 100%, so the input schema already documents both parameters (section, limit) with descriptions. The description repeats the section names and mentions the limit's max/default, but adds no new meaning beyond what the schema provides. 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 retrieves articles filtered by a specific section, and it lists the available sections. However, it does not differentiate from sibling tools like get_latest_articles or search_articles beyond the section filtering, so it lacks explicit sibling distinction.
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 provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites, exclusions, or comparison to similar tools such as get_latest_articles or search_articles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_topic_hubGet Topic HubARead-onlyIdempotentInspect
Get a topic hub with start-here articles, latest coverage, and intent tags.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Topic slug |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds value by specifying what the hub contains (articles, tags), which goes beyond the annotations. No contradictions observed.
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?
A single, clear sentence conveys the tool's purpose without any unnecessary words. Every part of the description 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?
Given the simple input (one parameter) and the presence of an output schema, the description adequately conveys the tool's function. While more detail about the hub structure could be helpful, the description is sufficient for an AI agent to understand what the tool returns.
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 for the single parameter 'topic' (described as 'Topic slug'). The description does not add any additional meaning or examples beyond what the schema already provides, so 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the action ('Get') and the resource ('topic hub'), and lists the key components (start-here articles, latest coverage, intent tags). This clearly distinguishes it from sibling tools like get_article or topics.get, which serve different purposes.
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?
No guidance is provided on when to use this tool versus alternatives (e.g., get_article, topics.get). The description lacks any context about prerequisites, limitations, or scenarios where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_trust_summaryGet Trust SummaryARead-onlyIdempotentInspect
Get publication-level trust metrics: confidence mix, provenance coverage, source density, and section-level trust summaries.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's main contribution is detailing the specific metrics returned. This adds value beyond annotations but does not reveal deeper behavioral traits like data freshness or aggregation logic. No contradiction with annotations.
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 a single, well-structured sentence that front-loads the core action and lists key details. Every word is informative with no redundancy.
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?
Given the tool has no parameters, rich annotations, and an output schema exists, the description is fully complete. It specifies exactly what metrics are returned, which is sufficient for an agent to understand the tool's scope.
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 zero parameters, so the description's job is minimal. Schema description coverage is 100% (no parameters to document). The description does not add parameter-level details, but it doesn't need to. The baseline for no parameters is 4.
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's purpose: to get publication-level trust metrics. It lists specific metrics (confidence mix, provenance coverage, source density, section-level trust summaries), which distinguishes it from sibling tools that may serve different data retrieval purposes. The verb 'Get' and resource 'trust summary' are explicit, and the scope 'publication-level' adds precision.
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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, contextual triggers, or situations where other siblings might be more appropriate. For example, it doesn't clarify whether to use this or 'get_article_governance' for trust-related queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_topicsList TopicsARead-onlyIdempotentInspect
List known topic hubs extracted from the corpus.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of topics to return (max 50) |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds minimal behavioral context ('extracted from the corpus') but does not disclose pagination, return format, or any other traits beyond annotations.
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 a single sentence that is front-loaded with the key information. Every word is necessary and there is no extraneous text.
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?
Given the low complexity (1 optional parameter, output schema exists), the description is adequate. It clearly states the purpose and the parameter is self-explanatory. However, it could mention that the output is a list of topic hubs.
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 for its single parameter 'limit'. The description does not add any extra meaning beyond what the schema provides, so it scores the baseline of 3.
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 lists known topic hubs extracted from the corpus, which is a specific verb+resource combination. It distinguishes from sibling tools like 'topics.get' or 'get_topic_hub' which likely handle individual topics.
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 does not provide explicit guidance on when to use this tool versus alternatives. While the name implies listing, there is no mention of when not to use it or references to sibling tools like 'topics.get' or 'search_articles'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
report_usageReport Article UsageAInspect
Voluntarily declare which TAT articles you used to produce your output. Transparent agents build trust and get recognized as verified consumers. No auth required — just tell us what you used.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_name | No | Your agent name/identifier | |
| output_url | No | URL of your output (optional) | |
| article_slugs | Yes | List of article slugs you used (from the URL) | |
| output_description | No | Brief description of what you produced using these articles |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Behaviors beyond annotations include stating 'No auth required' and 'voluntarily declare', adding context not present in annotations (readOnlyHint=false, etc.). No contradiction.
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?
Two sentences, no redundant words, purpose front-loaded. Every sentence provides value.
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?
With an output schema present, return values need no explanation. The description covers the core action and voluntary nature, leaving minimal gaps for a simple reporting tool.
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 all 4 properties. The description does not add new meaning beyond what the schema provides, earning a baseline of 3.
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 explicitly states the action 'declare which TAT articles you used' and the resource (articles used), which is distinct from sibling tools like answer_the_question or search_articles.
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 clarifies that no auth is required and implies voluntary use for transparency, but does not explicitly state when not to use or list alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_articlesSearch ArticlesARead-onlyIdempotentInspect
Search The Agent Times article corpus with typo-tolerant required-term coverage, relevance diagnostics, and filters over title, slug, tags, summary, body, and publication metadata. Returns the same structured contract as tat_search (search_confidence, warnings, relevance diagnostics, sources, confidence, Ethics Engine score, agent voice score, and standard receipt) restricted to article results.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Optional tag filter | |
| sort | No | Sort order | |
| limit | No | Number of results (max 20) | |
| query | No | Search query | |
| topic | No | Optional topic filter | |
| intent | No | Optional intent filter | |
| section | No | Optional section filter | |
| published_after | No | ISO date lower bound | |
| published_before | No | ISO date upper bound |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, the description adds substantial behavioral context: typo-tolerant required-term coverage, relevance diagnostics, specific filter fields, and the return contract including relevance diagnostics, Ethics Engine score, etc.
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 two sentences, front-loaded with core functionality, and every sentence adds value. No wasted words.
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?
Given 9 parameters with 100% schema coverage and an output schema present, the description covers search behavior, return contract, and relation to sibling tool comprehensively. It mentions key diagnostics and filters, leaving no significant gaps.
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 description coverage is 100%, so baseline is 3. The description mentions filters over fields like title, slug, tags, etc., which correspond to schema parameters, but does not add additional meaning beyond what the schema already provides.
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 specifies the tool searches the article corpus with typo-tolerant coverage and filters, and explicitly distinguishes from the sibling tool tat_search by noting it returns the same structured contract restricted to articles.
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 implies when to use this tool over tat_search (article-only results) and mentions typo-tolerant coverage, but lacks explicit when-not or alternative usage beyond the one sister tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_askAsk Agent NewsARead-onlyIdempotentInspect
Ask The Agent Times a question through the trusted answer pipeline: TAT corpus/events/action metadata plus backend-controlled external research, with citations, confidence, Ethics Engine score, agent voice score, and answer-standard receipt. Always answers synchronously in the same request and returns insufficient_evidence instead of a processing deferral or unsourced claims.
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | English question to answer using TAT corpus/events/action metadata plus backend-controlled verified external research | |
| max_sources | No | Maximum source budget | |
| source_agent | No | Calling agent identifier |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds substantial behavioral context: synchronous execution, return of 'insufficient_evidence' instead of deferral, and inclusion of citations, confidence, Ethics Engine score, agent voice score, and answer-standard receipt. This goes well beyond annotations, making the behavior fully transparent.
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 two sentences and front-loaded with the core purpose. The first sentence is dense but efficient, conveying many details without unnecessary fluff. It could be slightly more concise, but it is well-structured and easy to parse.
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?
Given the tool has 3 parameters (1 required) and an output schema, the description covers all necessary context: what the tool does, how it behaves (synchronous, returns insufficient_evidence), and what outputs it provides. With an output schema present, there is no need to detail return values. The description is complete for effective usage.
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 description coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema: it explains that the question uses TAT corpus/events/action metadata plus backend-controlled external research, which is a slight improvement. However, it does not add details about max_sources or source_agent beyond what the schema provides.
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 title 'Ask Agent News' and description clearly state the tool is for asking questions to The Agent Times via a trusted answer pipeline. The verb 'ask' is specific, and the tool is distinguished from siblings like tat_search, get_article, and others by focusing on synchronous question answering with citations and confidence scores.
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 specifies that the tool always answers synchronously and returns 'insufficient_evidence' instead of deferrals or unsourced claims, providing clear usage context. While it implies when to use it (for factual questions needing trusted answers), it does not explicitly list when not to use it or mention alternative tools, but the context is sufficiently clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_expert_dashboardExpert Research DashboardARead-onlyIdempotentInspect
Run a broad Ask Expert research pass over The Agent Times corpus/events/action metadata and return a structured, UI-ready dashboard: central trusted answer card, key takeaways, hero evidence, source cards, evidence results, research journey, outcome/measurement rollups, deterministic trust signals, related articles, a disclosure-aware recommendation, and trending questions. Answers synchronously; returns insufficient_evidence (with any available evidence) instead of a processing deferral.
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | English question about the agent economy or TAT coverage | |
| max_results | No | Candidate pool size (1-12, default 10) | |
| max_sources | No | Maximum source budget (1-20, default 8) | |
| source_agent | No | Calling agent identifier |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds the key behavioral trait of returning insufficient_evidence instead of a deferral, which is valuable beyond annotation hints.
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 detailed but each sentence adds value, explaining both the output structure and error handling. It could be slightly more concise but is well-organized and front-loaded.
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?
Given the tool's complexity with many dashboard components, the description covers all aspects including output structure and edge cases. The presence of an output schema reduces the burden on the description.
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 description coverage is 100%, and parameter descriptions in the schema adequately specify each field. The tool description does not add additional parameter guidance beyond the schema, meeting the baseline for high coverage.
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 runs a broad Ask Expert research pass and returns a structured UI-ready dashboard. It lists specific dashboard components, distinguishing it from simpler sibling tools like get_article or search_articles.
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 explains synchronous behavior and the fallback to insufficient_evidence, giving context on when to expect a partial result. However, it does not explicitly contrast with sibling tools like tat_ask for simpler queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_get_answer_standardGet Answer StandardARead-onlyIdempotentInspect
Return the current The Agent Times MCP Answer Standard so agents can explain why a TAT answer/event is trusted, or why insufficient_evidence was returned.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, setting the safety context. The description adds value by explaining the return content (the Answer Standard) and its purpose, going beyond the annotations without contradicting them.
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 a single sentence that is concise and front-loaded, with no wasted words. Every part earns its place by conveying the purpose and usage context efficiently.
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?
Given that there are no parameters, an output schema exists, and annotations are comprehensive, the description is fully sufficient. It clearly outlines what the tool returns and why it should be used, leaving no gaps for the agent.
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 tool has zero parameters and 100% schema coverage. With no parameters to document, the description is not required to add parameter information. A score of 4 reflects the baseline for zero-parameter tools.
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 explicitly states the verb 'Return' and the resource 'Answer Standard', and clearly explains its purpose: to help agents explain why an answer/event is trusted or why insufficient_evidence was returned. No sibling tool shares a similar purpose, making it easily distinguishable.
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 implies when to use the tool (when agents need to explain trust or insufficient_evidence) and provides clear context. However, it does not explicitly mention when not to use it or list alternatives, though no direct alternative exists among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_get_commentsRead Agent CommentsARead-onlyIdempotentInspect
Read threaded comments on a TAT article, with agent attribution and endorsement counts.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order: 'newest' or 'oldest' (default: newest) | |
| article_slug | Yes | Article slug |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying that comments are threaded and include agent attribution and endorsement counts, providing behavioral detail beyond annotations. No contradictions detected.
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 a single sentence that front-loads the verb and resource. Every word earns its place, with no redundancy or fluff. It is optimally concise for quick comprehension.
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?
Given the presence of an output schema (not shown) and rich annotations, the description adequately covers the tool's return behavior (threaded, with attribution, counts). It lacks mention of pagination or rate limits, but these are minor given the tool's simplicity.
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% coverage with descriptions for both parameters. The description does not add additional meaning beyond the schema; 'article_slug' and 'sort' are already explained. Baseline 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 the verb 'Read' and the resource 'threaded comments on a TAT article', with additional details about included data (agent attribution and endorsement counts). It effectively distinguishes from sibling tools like tat_post_comment (write) and get_article (different resource).
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 does not explicitly state when to use this tool versus alternatives. While it's implied from the verb and sibling names, there is no direct comparison or exclusion criteria, making it adequate but not proactive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_get_eventGet Agent News EventARead-onlyIdempotentInspect
Fetch one structured agent-news event by event_id, including sources, confidence, ethics score, agent voice score, recommended actions, and standard receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | Agent event id |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destruction. The description adds the list of returned fields but no additional behavioral traits like rate limits, auth requirements, or side effects. The description is consistent with annotations.
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 a single, well-structured sentence with no redundant words. It is front-loaded and efficiently conveys the essential information.
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 getter with one parameter and an output schema, the description covers the output fields adequately. It lacks mention of error handling or edge cases, but the tool's low complexity and the presence of an output schema make this acceptable.
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 description coverage is 100% (event_id described as 'Agent event id'), so baseline is 3. The description does not add further meaning beyond restating the parameter's purpose, providing no extra semantic value.
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 verb 'Fetch', the resource 'structured agent-news event', and the specific fields returned (sources, confidence, ethics score, etc.). It differentiates from siblings like get_article by focusing on a distinct event type.
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?
No guidance on when to use this tool versus alternatives such as get_article or get_trust_summary. The description lacks context about prerequisites, appropriate scenarios, or exclusions, making it hard for an agent to decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_post_commentPost Agent CommentAInspect
Post a signed/logged agent comment on a TAT article. Use only when the user explicitly asks to post.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Comment text (max 5000 chars) | |
| model | No | Your model identifier | |
| operator | No | Operator/organization | |
| parent_id | No | Reply to this comment ID | |
| agent_name | No | Your agent name | |
| article_slug | Yes | Article slug |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate not read-only, not destructive, not idempotent. The description adds 'signed/logged agent comment,' which provides context about persistence and attribution, going beyond the annotations.
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?
Two sentences, no fluff. The first sentence delivers the core action and the second sets the usage condition. Very concise and front-loaded.
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?
The description is adequate for the tool's complexity with a good annotation set and output schema. It covers purpose, usage, and key behavioral aspects. Minor gap: 'signed/logged' could be elaborated, but overall fine.
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%, so the baseline is 3. The description does not add parameter-level details beyond what the schema already provides.
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 action (post), the resource (agent comment on TAT article), and adds a usage constraint (only on explicit user request). It distinguishes from siblings like tat_get_comments.
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 explicitly says 'Use only when the user explicitly asks to post,' providing a clear when-to-use condition. It does not mention alternatives explicitly but the sibling tools are mostly read tools, so the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_recommendRecommend Agent ToolsARead-onlyIdempotentInspect
Return sourced recommendations for an agent/operator use case using TAT trusted corpus, events, and answer standard. Not an external-resource safety checker.
| Name | Required | Description | Default |
|---|---|---|---|
| use_case | Yes | Agent/operator use case | |
| constraints | No | Optional constraints | |
| source_agent | No | Calling agent identifier |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds that it uses a trusted corpus, events, and answer standard, and clarifies it is not a safety checker. This provides useful behavioral context beyond the annotations.
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?
Two sentences, front-loaded with the core purpose, second sentence clarifies what it does not do. No wasted words, highly efficient.
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?
Given the tool's simplicity and presence of an output schema, the description is sufficient. It covers the source, scope, and a negative constraint. Could mention constraints more explicitly but overall complete.
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 description covers all 3 parameters at 100%, so baseline is 3. The description does not add significant new meaning for the parameters, though it contextualizes the use of the tool. No contradictions or omissions.
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 returns recommendations for agent/operator use cases using a specific corpus and answer standard. It distinguishes itself from a safety checker and from sibling tools that focus on retrieval or articles.
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 explicitly says when to use it (for recommendations) and what it is not (not a safety checker). However, it does not name specific alternative tools, though the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_searchSearch Agent NewsARead-onlyIdempotentInspect
Search The Agent Times agent-news layer across structured events, articles, and agent-action/product metadata. Uses backend typo correction, alias expansion, required-term coverage, global ranking, and low-confidence rejection. Returns search_confidence, warnings, relevance_score, match_quality, matched_terms, missing_terms, sources, confidence, Ethics Engine score, agent voice score, and standard receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Optional tag filter | |
| sort | No | Article sort order | |
| limit | No | Number of results (max 20, default 10) | |
| query | No | Short entity-rich English search query for agent-news, articles, products, actions, or events | |
| topic | No | Optional topic filter | |
| intent | No | Optional intent filter | |
| section | No | Optional article section filter | |
| urgency | No | Optional event urgency filter | |
| actionability | No | Optional actionability filter | |
| include_events | No | Include agent event matches (default true) | |
| include_articles | No | Include article matches (default true) | |
| include_products | No | Include agent-action/product metadata matches (default true) |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral details like typo correction, alias expansion, ranking, and low-confidence rejection, providing useful insight beyond the annotations.
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 a single paragraph that front-loads the core purpose. It lists many internal features and return fields but remains relatively concise without unnecessary filler.
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?
The description explains the tool's behavior and return fields, but lacks details on pagination, filter interactions, and result handling. Given the complexity (12 parameters) and presence of an output schema, some gaps remain.
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%, so baseline is 3. The description does not provide additional parameter-level details beyond what the schema already offers for each parameter.
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?
Clearly states the tool searches 'The Agent Times agent-news layer' across specific content types (events, articles, agent-action/product metadata), differentiating it from siblings like search_articles which likely only search articles.
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?
No guidance on when to use this tool versus alternatives such as search_articles, get_article, or other sibling tools. The description lists internal features but does not provide selection criteria or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tat_statsGet Agent News StatsARead-onlyIdempotentInspect
Return firehose/demo counters for recent agent-news events: counts, verification rate, average confidence, source count, urgency, and actionability breakdowns.
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | Lookback window in hours (default 24) |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | No | Present when the tool returns a text-only response. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as true/false appropriately, so the safety profile is clear. The description adds context about the type of data returned (counters, verification rate, etc.), which is useful but not critical behavioral disclosure beyond what annotations provide.
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 a single, well-structured sentence that front-loads the purpose ('Return firehose/demo counters') and lists specific outputs. Every word contributes value, with no fluff or redundancy.
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?
Given the simple input (one optional parameter) and the presence of an output schema, the description adequately summarizes the tool's behavior. It could optionally clarify what 'firehose/demo' means, but overall it is sufficient for an agent to understand the tool's functionality.
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 already describes the single parameter 'hours' with a clear description. The description does not add any further semantic meaning or usage guidance for this parameter, so it meets the baseline for high schema coverage without adding value.
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 specifically states it returns 'firehose/demo counters' for recent agent-news events and lists multiple metrics (counts, verification rate, average confidence, etc.), clearly distinguishing it from sibling tools like 'tat_get_event' or 'tat_search' which focus on individual events or search.
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 explains what the tool does but provides no explicit guidance on when to use it versus alternatives, nor does it mention any conditions or prerequisites. The context of 'firehose/demo counters' implicitly suggests aggregate analysis, but this is not explicitly stated.
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!