create_orgCreate a team organization and seed its first project. Returns { orgId, projectId }.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Organization name. | |
| firstProjectName | No | Optional name for the seeded project. |
| Name | Required | Description | Default |
|---|---|---|---|
| orgId | Yes | ||
| projectId | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations providing destructiveHint=false and openWorldHint=false, the description adds useful behavioral context: creating the org also seeds a first project and returns both identifiers. It clearly communicates the primary side effect beyond the minimal annotation safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence that states the action, the side effect, and the return value. Every part is useful, and the core behavior is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the small parameter surface, full schema coverage, and presence of an output schema, the description sufficiently covers what the agent needs: the action, the seeded project behavior, and the return shape. No material gap remains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with each parameter already described in the input schema. The description adds slight context by tying firstProjectName to the seeded project and the return value, but does not significantly extend the parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Create') and resource ('team organization'), and clearly states the seeded first project as part of the action. It distinguishes itself from siblings like create_project by indicating this tool creates an organization plus its initial project, not just any project.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for creating an organization with an initial project and names the seeded project, but it does not explicitly contrast with create_project or other org/project tools. The context hints at the right time to use it, but the guidance is not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, and the descriptions clearly explain boundaries. However, list_diagrams/list_documents and get_board/get_board_image are two pairs that both concern the same underlying resource, so an agent could initially select the wrong one without reading carefully.
Nearly all tool names are snake_case verb_noun pairs such as create_project, update_document, and unpublish_listing, which is very consistent. The exceptions are bare 'draw' and the non-pattern 'whoami', so it is not a perfect 5.
With 38 tools, the surface exceeds the 25+ threshold and spans orgs, projects, documents, board drawing, membership, and marketplace publishing. While each subdomain is individually reasonable, the aggregate is heavy and likely to overwhelm an agent; several related actions could be grouped or exposed more sparingly.
The set covers the main lifecycle: org/project/document CRUD, board rendering and editing, member management, and template publish/use/update. Minor gaps remain—there is no get_project single-resource read, and groups/links/notes are manipulated only through the generic update_board rather than dedicated tools—but these are workable.