Skip to main content
Glama
devrev

DevRev MCP Server

Official
by devrev

get_vista

Retrieve sprint board details and associated sprint IDs from DevRev using a vista ID to filter and manage development workflows.

Instructions

Retrieve information about a vista in DevRev using its ID. In DevRev a vista is a sprint board which contains sprints (or vista group items). The reponse of this tool will contain the sprint (or vista group item) IDs that you can use to filter on sprints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe DevRev ID of the vista

Implementation Reference

  • Handler function implementing the 'get_vista' tool logic. Extracts 'id' from arguments, calls make_internal_devrev_request to 'vistas.get' endpoint, handles errors, and returns vista details.
    elif name == "get_vista":
        if not arguments:
            raise ValueError("Missing arguments")
    
        id = arguments.get("id")
        if not id:
            raise ValueError("Missing id ")
            
        response = make_internal_devrev_request(
            "vistas.get",
            {
                "id": id
            }
        )
        
        if response.status_code != 200:
            error_text = response.text
            return [
                types.TextContent(
                    type="text",
                    text=f"get_vista failed with status {response.status_code}: {error_text}"
                )
            ]
        
        return [
            types.TextContent(
                type="text",
                text=f"Vista details for '{id}':\n{response.json()}"
            )
        ]
  • JSON schema definition for the 'get_vista' tool input, requiring a 'id' string property.
    types.Tool(
        name="get_vista",
        description="Retrieve information about a vista in DevRev using its ID. In DevRev a vista is a sprint board which contains sprints (or vista group items). The reponse of this tool will contain the sprint (or vista group item) IDs that you can use to filter on sprints.",
        inputSchema={
            "type": "object",
            "properties": {
                "id": {
                    "type": "string",
                    "description": "The DevRev ID of the vista"
                }
             },
             "required": ["id"]
        },
    ),
  • Registration of the 'get_vista' tool in the handle_list_tools() function.
    types.Tool(
        name="get_vista",
        description="Retrieve information about a vista in DevRev using its ID. In DevRev a vista is a sprint board which contains sprints (or vista group items). The reponse of this tool will contain the sprint (or vista group item) IDs that you can use to filter on sprints.",
        inputSchema={
            "type": "object",
            "properties": {
                "id": {
                    "type": "string",
                    "description": "The DevRev ID of the vista"
                }
             },
             "required": ["id"]
        },
    ),
  • Utility function make_internal_devrev_request used by the get_vista handler to make authenticated POST requests to internal DevRev API endpoints.
    def make_internal_devrev_request(endpoint: str, payload: Dict[str, Any]) -> requests.Response:
        """
        Make an authenticated request to the DevRev API.
        
        Args:
            endpoint: The API endpoint path (e.g., "works.get" or "search.hybrid")
            payload: The JSON payload to send
        
        Returns:
            requests.Response object
        
        Raises:
            ValueError: If DEVREV_API_KEY environment variable is not set
        """
        api_key = os.environ.get("DEVREV_API_KEY")
        if not api_key:
            raise ValueError("DEVREV_API_KEY environment variable is not set")
    
        headers = {
            "Authorization": f"{api_key}",
            "Content-Type": "application/json",
        }
        
        return requests.post(
            f"https://api.devrev.ai/internal/{endpoint}",
            headers=headers,
            json=payload
        ) 
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as a retrieval operation, which implies it's read-only and non-destructive, but doesn't explicitly state this. It adds useful context about what a vista is and hints at the response content, but lacks details on error handling, rate limits, or authentication needs. The description adds some value but leaves gaps in behavioral transparency.

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 appropriately sized with two sentences that are front-loaded: the first sentence states the core purpose, and the second adds context about vistas and the response. There is no wasted text, and each sentence earns its place by clarifying the tool's function and utility. It could be slightly more structured but is efficient overall.

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 moderate complexity (single parameter, no output schema, no annotations), the description is somewhat complete. It explains what a vista is and hints at the response, but lacks details on return values, error cases, or integration with sibling tools. Without an output schema, more information on the response structure would be beneficial. The description is adequate but has clear gaps for full contextual understanding.

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 input schema has 100% description coverage, with the parameter 'id' documented as 'The DevRev ID of the vista'. The description adds no additional semantic details about the parameter beyond what the schema provides, such as format examples or constraints. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description, which applies here.

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's purpose: 'Retrieve information about a vista in DevRev using its ID' with the specific verb 'retrieve' and resource 'vista'. It distinguishes the tool by explaining that a vista is a 'sprint board which contains sprints (or vista group items)', which helps differentiate it from sibling tools like 'get_sprints' or 'get_work'. However, it doesn't explicitly contrast with similar retrieval tools like 'get_part' or 'get_work', keeping it from a perfect score.

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 by stating 'using its ID' and mentions the response can be used to 'filter on sprints', which suggests a context for when to use this tool. However, it lacks explicit guidance on when to choose this over alternatives like 'get_sprints' or 'list_parts', and doesn't specify prerequisites or exclusions. The guidance is present but not comprehensive.

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/devrev/mcp-server'

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