Skip to main content
Glama

Ask AI

by com.ask-ai-data-connector
OverviewDiscussionsAdmin

get_insights

Get the business improvement checklist (the FINDINGS to act on). If insights exist, returns the current checklist with status. If no insights exist (or refresh is requested), returns a data bundle with all key metrics from connected sources — use this data to generate actionable business recommendations (typically 3–8, as many as the data supports), then call save_insights to store them. You can also call save_insights with a single insight at any time during conversation. Use report: 'thread' (with threadId or insightId) to retrieve a linked sequence of related findings as one story. NOTE: 'did the fix work' / win-rate / outcomes are NOT here — insights are observations. Once a fix ships, set_intervention flips the finding to 'addressed' and the outcome lives on the intervention; call get_interventions(report: 'outcomes') for that. Filter by category, tags, or threadId to narrow the list. Each returned item includes threadId, parentInsightId, and a threadCount so you can spot follow-up chains without an extra call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter to insights that contain ANY of these tags (OR semantics). E.g. ['seo'] or ['paid'].
reportNoDefault: 'checklist'. 'thread' retrieves a linked sequence of related findings as one story — requires threadId or insightId. (For fix outcomes / win-rate, use get_interventions(report: 'outcomes').)
statusNoFilter by status. Pass a single value (e.g. 'open') or an array (e.g. ['open','addressed']) for OR semantics. Allowed values: open, addressed, superseded, dismissed.
_offsetNoPagination offset. If a response includes _pagination.hasMore=true, use _offset to fetch the next page.
refreshNoSet to true to generate fresh insights even if existing ones are present. Default: false — returns existing checklist.
categoryNoFilter to a single category.
threadIdNoFilter to a single thread (works on checklist and thread reports). Used to view a story end-to-end without category/tag filtering.
insightIdNoFor report: 'thread' — resolve the threadId from this insight and return the full thread (alternative to passing threadId directly).
includeCompletedNoDefault true. Set to false to return only active (open) insights.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and discharges it: it discloses the conditional dual-mode return (existing checklist vs. a metrics data bundle that mandates downstream generation), the follow-up chain metadata (threadId, parentInsightId, threadCount), and the refresh semantics. It also proactively rules out outcome/win-rate data, preventing a likely misuse.

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?

Front-loaded with the core purpose, then layered with usage, exclusions, and return metadata. It is longer than most definitions, but nearly every sentence carries actionable routing or return-shape information, so little is wasted.

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 9-parameter, no-annotation, no-output-schema tool, this cooperates well with the siblings, explains what gets returned in both branches, and pins down the follow-up chain fields an agent needs to traverse threads without an extra call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all nine parameters, including the report enum, threadId/insightId relationship, and refresh. The description only restates the high-level usage of report/threadId and filtering, adding little beyond what the schema fields already convey.

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?

States a specific verb+resource ('the business improvement checklist (the FINDINGS to act on)') and immediately distinguishes it from other insight-adjacent tools by defining insights as observations, not outcomes. An agent can read this and know exactly what get_insights returns versus get_interventions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use save_insights after generating recommendations, use set_intervention to flip a finding to 'addressed' once a fix ships, and use get_interventions(report: 'outcomes') for win-rate/outcome questions. It also states the refresh trigger and when to use report: 'thread'.

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

All Ask AI 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