Skip to main content
Glama

org_create

Create a new organization in the Technical Project Manager system to structure and manage hierarchical projects, features, and tasks.

Instructions

PROJECT MANAGEMENT: Create a new organization (rarely needed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOrganization name

Implementation Reference

  • Tool registration for 'org_create' in the MCP server list_tools function, defining name, description, and input schema.
    Tool(
        name="org_create",
        description="PROJECT MANAGEMENT: Create a new organization (rarely needed).",
        inputSchema={
            "type": "object",
            "properties": {"name": {"type": "string", "description": "Organization name"}},
            "required": ["name"],
        },
    ),
  • MCP tool handler in _handle_tool that parses args, creates OrgCreate model, calls db.create_org, and returns JSON response.
    if name == "org_create":
        org = db.create_org(OrgCreate(name=args["name"]))
        return f"Created org: {_json(org)}"
  • Pydantic input model OrgCreate defining the required 'name' field for organization creation.
    class OrgCreate(BaseModel):
        name: str
  • Database helper method in TrackerDB that generates ID, inserts org into SQLite 'orgs' table, and returns Org model.
    def create_org(self, data: OrgCreate) -> Org:
        id = self._gen_id()
        now = self._now()
        self.conn.execute(
            "INSERT INTO orgs (id, name, created_at) VALUES (?, ?, ?)", (id, data.name, now)
        )
        self.conn.commit()
        return Org(id=id, name=data.name, created_at=datetime.fromisoformat(now))
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'rarely needed', which adds some behavioral context about frequency, but does not disclose critical traits like permissions required, whether it's a mutation (implied by 'Create'), side effects, or error handling. This leaves significant gaps for a tool that likely modifies system state.

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?

The description is extremely concise with two parts: the action ('Create a new organization') and usage note ('rarely needed'). Every word earns its place, and it is front-loaded with the core purpose. There is no wasted text or 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?

Given the tool's complexity (a mutation with no annotations and no output schema), the description is minimally adequate. It states the purpose and usage frequency but lacks details on behavioral traits, return values, or error cases. For a creation tool, more context would be helpful, but it meets the basic threshold.

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?

The schema description coverage is 100%, with the parameter 'name' fully documented in the schema. The description does not add any parameter-specific details beyond what the schema provides, such as format constraints or examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 clearly states the verb ('Create') and resource ('a new organization'), making the purpose specific and understandable. It distinguishes from siblings like 'org_list' by indicating creation rather than listing. However, it doesn't fully differentiate from other creation tools like 'project_create' or 'ticket_create' beyond the resource type.

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?

The description provides explicit guidance with 'rarely needed', which helps the agent understand this is for infrequent use cases. It implies context for when to use it (e.g., initial setup), but does not specify alternatives or exclusions, such as when to use 'org_list' instead or prerequisites for creation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/urjitbhatia/tpm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server