Skip to main content
Glama

list_all_wikis_in_organization

Discover all wikis across projects in your Azure DevOps organization to find documentation and enable cross-project collaboration.

Instructions

List all wikis across all projects in the organization for cross-project discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function that implements the tool logic. It fetches all projects in the organization, retrieves wikis for each project using self.get_wikis(), collects wiki details (project, id, name, url, remote_url), handles exceptions by skipping inaccessible projects, and returns the aggregated list of all wikis.
    def list_all_wikis_in_organization(self):
        """
        List all wikis across all projects in the organization.
        """
        projects = self.get_projects()
        all_wikis = []
        
        for project in projects:
            try:
                wikis = self.get_wikis(project.name)
                for wiki in wikis:
                    all_wikis.append({
                        "project": project.name,
                        "id": wiki.id,
                        "name": wiki.name,
                        "url": wiki.url,
                        "remote_url": wiki.remote_url,
                    })
            except Exception:
                # Skip projects where we can't access wikis
                continue
        
        return all_wikis
  • Registers the tool with the MCP server using types.Tool(), providing the name, description, and input schema (empty object since no parameters are required). This makes the tool available via @self.server.list_tools().
    types.Tool(
        name="list_all_wikis_in_organization",
        description="List all wikis across all projects in the organization for cross-project discovery.",
        inputSchema={
            "type": "object",
            "properties": {},
            "additionalProperties": False
        }
    ),
  • Defines the input schema for the tool: an empty object with no properties, indicating the tool takes no input parameters.
        inputSchema={
            "type": "object",
            "properties": {},
            "additionalProperties": False
        }
    ),
  • Server-side dispatch handler in _execute_tool() that receives tool calls and delegates execution to the client's list_all_wikis_in_organization() method.
    elif name == "list_all_wikis_in_organization":
        return self.client.list_all_wikis_in_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 but only states what the tool does, not how it behaves. It lacks information about permissions needed, rate limits, pagination, return format, or whether it's a read-only operation. For a list operation with zero annotation coverage, this is insufficient behavioral disclosure.

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 a single, well-constructed sentence that efficiently communicates the tool's purpose and context. Every word earns its place, with no redundant information or unnecessary elaboration.

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 zero-parameter list tool with no output schema, the description adequately covers the basic purpose and scope. However, without annotations or output schema, it should ideally provide more behavioral context about what information is returned and any limitations. The description is complete enough for basic understanding but lacks operational details.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the empty input. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose and usage context.

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?

The description clearly states the specific action ('List all wikis') and resource ('across all projects in the organization'), distinguishing it from sibling tools like 'get_wikis' or 'find_wiki_by_name' which likely have different scopes. It explicitly mentions 'cross-project discovery' which clarifies the organizational-level scope.

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 clear context for when to use this tool ('for cross-project discovery'), implying it's for broad organizational overviews rather than project-specific queries. However, it doesn't explicitly state when not to use it or name specific alternatives like 'get_wikis' for project-level listing.

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/xrmghost/mcp-azure-devops'

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