独行录 / opcmenu

配置组织邀约电话授权

update_organization_meetup_outreach_access

仅平台管理员；先预览员工、来源、每日人数上限和开关，再同参+previewHash、consent=true、preview=false保存。仅授权此组织GROUP人工邀约，人员来源仍逐次核验；不授予真人登录电话或通用查看权，不代拨电话。

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>",
      "value": "<value>",
      "expectedUpdatedAt": "<expectedUpdatedAt>"
    },
    "name": "update_organization_meetup_outreach_access"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`consent`	No
`preview`	No
`previewHash`	No
`organizationId`	Yes
`expectedUpdatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the admin-only gate, the two-phase preview/commit protocol with hash matching, and the exact consent flag requirement. Gaps remain around concurrency (expectedUpdatedAt optimistic locking is never explained) and what happens on a hash mismatch or stale updatedAt.

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?

One compact, front-loaded block: admin restriction first, then procedure, then scope limits. Dense but every clause carries information; the semicolon-chained style is slightly hard to parse but not wasteful.

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?

For a 6-param nested mutation with no output schema and no annotations, the description covers authorization, the commit protocol, and the scope boundary. It omits where previewHash comes from and the meaning of expectedUpdatedAt, which are the remaining blockers for a fully correct invocation.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: 开关 (enabled), 来源 (allowedSources), 员工 (allowedUserIds), 每日人数上限 (dailyDistinctLimit), previewHash, consent and preview are all given meaning. organizationId and expectedUpdatedAt are left unelaborated.

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?

The description names a specific verb and resource: configuring this organization's GROUP manual-outreach access (switch, sources, per-day cap, allowed employees). It differentiates itself from the sibling update_organization_meetup_outreach by explicitly limiting scope to 'authorizing GROUP manual outreach' and disclaiming phone login/dialing rights.

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?

It states the precondition (platform admins only) and prescribes the call sequence: preview first, then re-submit with identical params plus previewHash, consent=true, preview=false. It also lists what the tool does not authorize. It does not, however, say when to prefer it over update_organization_meetup_outreach or how to obtain previewHash.

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?