Skip to main content
Glama

application_info

Retrieve comprehensive details for a specific candidate application using its unique ID to support hiring decisions and pipeline management.

Instructions

Get full details for a single application by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationIdYesThe application ID (UUID)

Implementation Reference

  • The handle_call_tool function is the handler that dynamically routes tool calls to Ashby API endpoints using the TOOL_ENDPOINT_MAP. This handles the 'application_info' tool by mapping it to '/application.info' and posting the request.
    @server.call_tool()
    async def handle_call_tool(name: str, arguments: dict[str, Any]) -> list[types.TextContent]:
        """Route tool calls to the correct Ashby endpoint, passing arguments directly."""
        endpoint = TOOL_ENDPOINT_MAP.get(name)
        if not endpoint:
            return [types.TextContent(type="text", text=f"Unknown tool: {name}")]
    
        try:
            # Pass arguments straight through -- tool schemas already use Ashby's
            # camelCase param names so no translation is needed.
            response = ashby.post(endpoint, data=arguments if arguments else None)
            return [types.TextContent(type="text", text=json.dumps(response, indent=2))]
        except requests.exceptions.HTTPError as e:
            error_body = ""
            if e.response is not None:
                try:
                    error_body = e.response.text
                except Exception:
                    pass
            return [
                types.TextContent(
                    type="text",
                    text=f"Ashby API error on {endpoint}: {e}\n{error_body}",
                )
            ]
        except Exception as e:
            return [types.TextContent(type="text", text=f"Error calling {endpoint}: {e}")]
  • The tool 'application_info' is registered within the TOOLS list, which provides the name, description, and input schema for the tool.
    types.Tool(
        name="application_info",
        description="Get full details for a single application by ID.",
        inputSchema={
            "type": "object",
            "properties": {
                "applicationId": {"type": "string", "description": "The application ID (UUID)"},
            },
            "required": ["applicationId"],
        },
    ),
  • The tool 'application_info' is mapped to the API endpoint '/application.info' in the TOOL_ENDPOINT_MAP.
    "application_info": "/application.info",
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't clarify permissions, rate limits, error handling, or what 'full details' includes. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, scope, and required input, making it highly concise and well-structured.

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 simplicity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose but lacks behavioral details and usage context, which are important even for simple tools. It meets minimum viability but has clear gaps in guidance and transparency.

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 'applicationId' documented as a UUID. The description adds minimal value beyond the schema, as it only reiterates the need for an ID without providing additional context like format examples or validation rules. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Get full details') and resource ('for a single application by ID'), making the purpose immediately understandable. It distinguishes this as a retrieval tool for individual applications rather than bulk operations, though it doesn't explicitly differentiate from similar tools like 'candidate_info' or 'job_info' which follow the same pattern.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'application_list' for multiple applications or 'candidate_info' for related data, nor does it specify prerequisites such as needing an application ID. Usage is implied but not articulated.

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/PlenishAI/mcp-ashby'

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