Skip to main content
Glama

List live contexts

list_live_contexts
Read-onlyIdempotent

List live contexts that Studio injects into chats. Use it to inspect available context rows per workspace, returning JSON items up to a set limit; read-only.

Instructions

List Live Contexts that Studio injects into chats. Use list_context_studio for attachment files, and get_studio_entity for one row. Read-only. Returns JSON items up to limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_live_contexts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows. Integer from 1 to 500. Default 100.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  3. Addedv6.1.5

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description clarifies the content scope ('Studio inject into chats') and operational behavior regarding the response structure ('Returns JSON items up to limit'). It is highly focused on the intent and output format rather than merely restating safety hints.

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?

The definition is extremely concise, front-loading the purpose and immediately providing critical context via sibling comparisons. Every phrase serves a high functional purpose without redundancy.

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?

Given the clear scope, the definition is highly complete. The combination of specific resource naming, sibling guidance, and operational limits means an agent has all necessary information to use this tool correctly and safely.

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?

With 100% schema description coverage, the input schema thoroughly documents the parameters (limit, workspace). The description does not add meaningful semantic information to these technical fields, fitting the baseline score for high coverage.

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?

The description explicitly defines the target resource ('Live Context') and the mechanism ('Studio inject into chats'). It distinguishes this tool's purpose from related tools by specifying that it handles the general list of contexts, unlike siblings that handle attachments or single rows.

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?

The description provides explicit routing logic for edge cases: if the user needs attachment files, they must use 'list_context_studio', and for fetching a single row, they must use 'get_studio_entity'. This eliminates common ambiguity for the agent.

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