Context Link

Get Context

get_context

Read-onlyIdempotent

Get context from the user's connected workspaces and websites. The attached widget displays only the list of sources consulted — it does not show the retrieved content, so use the returned context to answer the user directly.

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": "get_context"
  }
}

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	Default
`context`	Yes
`sources`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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"
+}

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint). The description adds genuinely non-obvious behavioral context beyond them: the attached widget shows only the source list, not the retrieved content, so the agent must consume and relay the returned context itself. That is a real UI/side-effect disclosure not present in structured fields.

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 sentences, zero padding, and the primary capability is front-loaded before the caveat. Every clause earns its place, including the widget warning.

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 no explanation, and the description covers both the retrieval action and the widget caveat. The remaining gap is routing guidance relative to get_memory/ask_question, which is absent.

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 67%, and the description adds nothing about mode, query, or connection_type. The undocumented query parameter (0% covered, and required) is not compensated for, but the other two parameters carry adequate schema descriptions, so the baseline 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?

States a specific verb and resource: retrieve context from the user's connected workspaces and websites. This distinguishes it from get_memory (stored memory) reasonably well, though it never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

Gives useful downstream guidance ('use the returned context to answer the user directly') but never says when to call this versus get_memory or ask_question. The condition for choosing this tool is implied by the term 'context' rather than specified.

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?