Context Link

Ask Question

ask_question

Read-onlyIdempotent

Ask a question about the user's connected workspaces and websites and receive a concise answer with citations. The attached widget displays only the list of sources consulted — it does not show the answer, so always relay the answer text in your reply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "ask_question"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Optional mode to weight results (e.g. 'customer-support')
`query`	Yes
`connection_type`	No	Optional comma-separated list of connection types to restrict retrieval to (e.g. "site,email"). Only content from those sources is considered. Valid types: basecamp, custom, email, files, google_doc, memory, monday, notion, one_drive, site, webmention, youtube.

Output Schema

Name	Required	Description
`answer`	Yes	Concise paragraph answer; empty string when success is false
`reason`	Yes
`sources`	Yes
`success`	Yes
`citations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 12, 2026

addedInput schema / properties / connection_type

Added value: +{
+  "description": "Optional comma-separated list of connection types to restrict retrieval to (e.g. \"site,email\"). Only content from those sources is considered. Valid types: basecamp, custom, email, files, google_doc, memory, monday, notion, one_drive, site, webmention, youtube.",
+  "type": "string"
+}

changedOutput schema / properties / reason / enum

Previous value: -[
-  "ok",
-  "no_context",
-  "llm_error",
-  "empty_input",
-  "auth_required",
-  "signup_required",
-  "pro_required",
-  "allowance_exceeded"
-]New value: +[
+  "ok",
+  "no_context",
+  "llm_error",
+  "empty_input",
+  "auth_required",
+  "signup_required",
+  "pro_required",
+  "allowance_exceeded",
+  "invalid_connection_type"
+]

First observedSep 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the attached widget shows only the source list, not the answer, so the agent must relay the answer text itself. That is practical disclosure beyond the structured fields, though it stops short of describing scoping or result quality behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: purpose first, then the widget/relay caveat. No filler and each sentence carries information the agent needs.

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

Completeness4/5

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

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description covers the critical output-relay gotcha, but omits any mention of restricting retrieval via connection_type/mode or what kind of query text is expected, leaving a small gap.

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 67%, with 'mode' and 'connection_type' documented in the schema and 'query' undocumented. The description adds no parameter-level meaning at all, so it does not compensate for the undocumented query field; baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb+resource: ask a question about the user's connected workspaces and websites, returning a concise answer with citations. It clearly distinguishes the retrieval/Q&A role from memory siblings like get_memory and save_memory, though it never names an alternative tool explicitly.

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?

Usage is implied by the 'ask a question... receive an answer with citations' framing, giving the agent a reasonable sense of when this tool fits. However, there is no guidance on when to prefer this over get_context or get_memory, and no stated conditions or exclusions for using it.

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

All Context Link tools Inspect

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

Need Help?