Skip to main content
Glama
Sign In
Local AI Relay

Local AI Relay

by zxc972
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

chat_status

Read-only

Checks room members, background listening, and wake-up status on demand so agents can verify local relay delivery without polling in a model loop.

Instructions

按需查看成员、后台监听和唤醒状态；不要用模型循环检查。

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": {
      "room": "<room>"
    },
    "name": "chat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYes
serverNo网络房间的 http(s) 服务地址；省略为本机房间
session_idNo当前独立会话的固定 ID；新接入必填并在所有调用中沿用。有原生 thread_id 时须相同，否则本会话生成一次 UUID。省略仅兼容旧接入。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description only adds the anti-polling behavioral guidance and the on-demand framing; it says nothing about what the returned status contains, its freshness, or whether it observes remote rooms. Adequate but not rich 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.

Conciseness5/5

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

One front-loaded sentence carrying the action, the scope, and the anti-pattern warning. Nothing is padded and nothing is buried.

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

Completeness3/5

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

No output schema exists, so the description carries the burden of explaining what 'status' means, and it doesn't — an agent cannot foresee the shape or contents of the result. For a 3-parameter status tool with one undocumented required param, this is the minimum viable, not complete.

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

Parameters2/5

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

Schema coverage is only 67%, and the single required parameter (room) has no schema description at all — a real gap the description does nothing to fill. It also doesn't explain how server and session_id interact when querying a remote room. Baseline would be 3 at high coverage, but here the undocumented required param pulls it lower.

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?

Names a specific verb (查看/view) and three concrete status facets: members, background listening, and wakeup. An agent can distinguish it from chat_receive (which fetches messages) and from chat_context. It stops short of 5 because the '唤醒状态' facet is jargon-heavy and the description doesn't state the resource granularity (room-level vs session-level).

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

Usage Guidelines4/5

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

Explicitly says to call on demand ('按需') and warns against model loop-checking, which is a real and useful when-not-to-use rule. It does not name an alternative sibling (e.g., chat_checkpoint or chat_context) for the near-miss cases, so it lacks the full when/when-not/alternatives triad.

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

Deploy Server

Other Tools