Skip to main content
Glama
Sign In
dayuan-lite

dayuan-lite

by lighters
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dayuan_status

Read-only

Checks the local configuration status of the dayuan-lite MCP server without making remote requests, clarifying that local setup does not confirm authorization is still valid.

Instructions

本地配置状态；不发起远端请求，不代表授权仍有效。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

openWorldHint=false and readOnlyHint=true already tell the agent this is a safe, non-networked read, so "不发起远端请求" largely repeats the annotations. The added caveat that a status result does not imply valid authorization is genuinely new context and prevents misinterpretation, but nothing is said about staleness, caching, or what the status covers.

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?

A single short sentence with the purpose front-loaded and no filler. The terseness borders on cryptic, but every clause (local only, not proof of auth) contributes meaning.

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?

There is no output schema and the description never indicates what the local configuration status contains or how fresh it is, which is the main thing an agent needs before deciding to rely on the result. Given the tool's simplicity, this is an adequate but incomplete definition.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to carry; the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"本地配置状态" names the resource (local configuration) but supplies no verb and no scope detail, so the agent must infer that the tool reads status. Nothing distinguishes it from the sibling dayuan_capabilities, which plausibly also reports local capability/config state.

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

Usage Guidelines2/5

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

It gives a negative condition — the result does not mean authorization is still valid — which hints at when not to trust it, but names no alternative tool for checking auth (e.g. dayuan_capabilities) and states no positive trigger for calling it.

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