Skip to main content
Glama

独行录 / opcmenu

创建我的公司

create_company
Idempotent

【需要登录】为当前用户创建一人公司主页(每个用户最多一家;已存在则等价于更新)。slug 全局唯一(被别人占用会报 slug_taken)。

【发布】先过后审:立即生效,后台异步风控审计。

【提示】description 越详细,主页内容质量越高。建到了就可以在引导里 complete_onboarding。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes公司 / 工作室名称
sizeNo团队规模,可选:SOLO(一人公司) | SIZE_2_5(2-5 人) | SIZE_6_10(6-10 人) | SIZE_11_50(11-50 人) | SIZE_50_PLUS(50 人以上)
slugYes公司主页 URL 标识,小写字母/数字/连字符,全局唯一
logoUrlNoLogo 图 URL,可选
taglineNo一句话定位,可选
locationNo所在地,可选
websiteUrlNo官网 URL,可选
descriptionNo详细介绍:在做什么、为谁做、进展,越详细内容质量越高
foundedYearNo成立年份,可选

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

在 annotations 只提供 readOnlyHint/idempotentHint 等布尔提示的情况下,描述额外披露了需要登录、先过后审的异步风控、slug 全局唯一及 slug_taken 错误、description 影响内容质量。这些是调用方做决策和预期管理的重要行为信息,且与 idempotentHint=true 一致,无矛盾。

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?

用三个短段落【需要登录】【发布】【提示】结构化呈现,第一句就点明核心用途,后续每句都携带独立信息,无冗余。

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?

对于无 output schema 的创建类工具,描述覆盖了登录要求、幂等 upsert、唯一性错误、审核机制和后续动作,已经相当完整;唯一缺口是没有说明成功后的返回内容,但这个缺失不严重影响工具选择与调用。

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 对 9 个参数覆盖 100%,已承担主要说明责任;描述额外补充了 slug 的全局唯一性与冲突错误,以及 description 越详细内容质量越高这一语义,提升了参数的理解价值。

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?

明确说出“为当前用户创建一人公司主页”,动词+资源+归属都清楚;还补充“已存在则等价于更新”“每个用户最多一家”,把 create 工具的实际 upsert 行为讲明,能与其他 get/list 类公司工具区分开。

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?

给出了明确使用场景:当前用户、最多一家、已存在则更新,并指示“建到了就可以在引导里 complete_onboarding”。虽然没有点名替换工具 update_my_company,但“已存在则等价于更新”已经隐含了覆盖更新场景的路由语义。

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Each tool has a clearly documented purpose, often with explicit 'when to use' guidance and cross-references, making the vast majority easy to tell apart. A few clusters (get_my_brief, get_my_positioning, get_my_work, get_my_dispatch) and data-overlapping get_my_card vs get_my_profile require careful reading, but descriptions are detailed enough to prevent serious misselection.

Naming Consistency4/5

The overwhelming majority follow snake_case verb_noun conventions (create_product, update_need, list_my_signups). Minor deviations include noun-only feed names (personalized_feed, random_feed), inconsistency between 'prefs' and 'preferences' in notification tools, and a mix of update_* and set_* for mutations, but the pattern remains predictable overall.

Tool Count1/5

137 tools is an extreme mismatch for any MCP server, far exceeding the 50+ threshold for a score of 1. Even with a broad multi-domain platform, this volume makes tool selection and navigation impractical and heavily burdens the agent's context window.

Completeness5/5

The surface covers full lifecycles for needs, products, activities/signups, conversations, collaboration goals/tasks, dispatch, profile/onboarding, and supporting resources like companies, parks, policies, and ratings. Deliberate omissions (no user-post creation, no organizer profile editing via agent) are explicitly documented, so core workflows have no obvious dead ends.

Resources