独行录 / opcmenu

查看本组织经营统计

get_organization_analytics

Read-only

登录/当前工作人员；按职责读取本组织1/7/30/90天新增、等长上期、日趋势、当前状态分布与待办，上海时间含今天。未授权模块不提供数据；状态分布和待办不受新增时间窗限制。预约不等于履约、奖励不等于营收，不含浏览量、租金、出租率、能耗或财务流水。

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": {
      "organizationId": "<organizationId>"
    },
    "name": "get_organization_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`organizationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

标注只说明 `readOnlyHint: true`，描述则补充了：未授权模块不提供数据；状态分布与待办不受新增时间窗口限制；日界按上海时间并包含今天；还说明了数据口径限制（预约不等于履约、奖励不等于营收，不含浏览量、租金等）。它仍未描述返回结构、聚合粒度，也未说明 `organizationId` 无效时的行为。

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?

开头就给出读者与范围，再补充口径说明，整体紧凑。句子信息密度高，用分号串起多个子句，符合多指标报表工具的体量，但行话多、电报式风格稍影响可读性。

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?

这个只读分析工具没有输出 Schema，但描述已覆盖范围、时间语义、权限和指标口径，基本够用。缺少响应结构说明、待办项如何识别，以及稀疏数据时上期对比是否失败等边界情况。

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 描述覆盖率为 0%，描述承担了主要说明责任；它解释 `days` 选择 1/7/30/90 的新增窗口，并会与等长上期对比，这超出了枚举本身。但 `organizationId` 未解释，默认 7 天的行为也未说明。

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?

本组织经营统计是一个具体的指标资源，范围包括新增数量、上期对比、趋势、状态分布和待办。它与 `get_organization` 及 `list_organization_audit` 等工具能区分开。略微失分，是因为中文短语较简略，且“待办”等指标没有定义。

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?

“登录/当前工作人员”和“按职责”暗示了权限范围与工作人员用途，但没有明确说明何时该选它，而不是其他组织级读取工具。也没有指出何时不应使用，或点名可替代的工具。

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

All 独行录 / opcmenu 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?