Skip to main content
Glama
singlestore-labs

SingleStore MCP Server

organization_info

Access organization details in SingleStore, including unique orgID and display name, for effective user context and system integration.

Instructions

Retrieve information about the current user's organization in SingleStore.

Returns organization details including:
- orgID: Unique identifier for the organization
- name: Organization display name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxNo

Implementation Reference

  • The primary handler function implementing the organization_info tool. It fetches the current organization details using a utility function, tracks analytics, and returns formatted organization information including orgID and name.
    def organization_info() -> dict:
        """
        Retrieve information about the current user's organization in SingleStore.
    
        Returns organization details including:
        - orgID: Unique identifier for the organization
        - name: Organization display name
        """
        start_time = time.time()
        settings = config.get_settings()
        user_id = config.get_user_id()
        settings.analytics_manager.track_event(
            user_id, "tool_calling", {"name": "organization_info"}
        )
    
        org = utils.fetch_organization()
        execution_time = (time.time() - start_time) * 1000
    
        return {
            "status": "success",
            "message": f"Retrieved organization information for '{org.name}'",
            "data": {
                "orgID": org.id,
                "name": org.name,
            },
            "metadata": {
                "execution_time_ms": round(execution_time, 2),
                "timestamp": datetime.now(timezone.utc).isoformat(),
            },
        }
  • Central registration of the organization_info tool (and others) in the tools_definition list, which is used to create Tool instances for the MCP server.
    tools_definition = [
        {"func": get_user_info},
        {"func": organization_info},
        {"func": choose_organization},
        {"func": set_organization},
        {"func": workspace_groups_info},
        {"func": workspaces_info},
        {"func": resume_workspace},
        {"func": list_starter_workspaces},
        {"func": create_starter_workspace},
        {"func": terminate_starter_workspace},
        {"func": list_regions},
        {"func": list_sharedtier_regions},
        {"func": run_sql},
        {"func": create_notebook_file},
        {"func": upload_notebook_file},
        {"func": create_job_from_notebook},
        {"func": get_job},
        {"func": delete_job},
    ]
    
    # Export the tools
    tools = [Tool.create_from_dict(tool) for tool in tools_definition]
  • Supporting utility function called by the organization_info handler to fetch the current organization object via SingleStore's workspace manager.
    def fetch_organization():
        """
        Returns the organization object using the workspace manager.
        """
        settings = config.get_settings()
        workspace_manager = s2.manage_workspaces(
            access_token=get_access_token(),
            base_url=settings.s2_api_base_url,
            organization_id=get_org_id(),
        )
        return workspace_manager.organization
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation (read-only) and describes what information is returned, but doesn't mention authentication requirements, rate limits, error conditions, or whether this requires specific permissions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is efficiently structured with a clear purpose statement followed by bullet points of returned information. Both sentences earn their place by providing essential information without redundancy. The bullet format enhances readability while maintaining brevity.

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?

For a read-only information retrieval tool with no output schema, the description provides the core purpose and return format details. However, without annotations and with sibling tools that might overlap (like 'get_organizations'), the description could better clarify this tool's specific niche and any behavioral constraints.

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?

The tool has only one parameter (ctx) with 0% schema description coverage. The description doesn't mention parameters at all, which is acceptable since this appears to be a context injection parameter rather than a user-facing input. For a tool with effectively zero user-facing parameters, a score of 4 is appropriate as the description focuses on what the tool does rather than parameter documentation.

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 tool retrieves organization information for the current user in SingleStore, specifying the verb 'retrieve' and resource 'organization details'. It distinguishes from sibling 'get_organizations' by focusing on the current user's organization rather than listing all organizations.

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?

The description implies usage context by specifying 'current user's organization', suggesting this tool is for getting details about the user's own organization. However, it doesn't explicitly state when to use this versus 'get_organizations' or other sibling tools, nor does it mention prerequisites or exclusions.

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

Related 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/singlestore-labs/mcp-server-singlestore'

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