Skip to main content
Glama
loaditoutadmin

loaditout-mcp-server

Official

check_permission

Verify whether a permission request has been approved, denied, or remains pending by providing the request ID.

Instructions

Check the status of a previously submitted permission request. Returns a JSON object with status ('pending', 'approved', or 'denied'). Use this after calling request_permission to poll for the human owner's decision. Do not call this without a valid request_id from a prior request_permission call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYesThe request ID returned from request_permission

Implementation Reference

  • The handler function that executes the check_permission tool logic. Makes an HTTP GET request to the permission API endpoint with the agent key and request_id, and returns the permission status ('pending', 'approved', or 'denied').
    async function handleCheckPermission(args: {
      request_id: number;
    }): Promise<string> {
      const params = new URLSearchParams({
        agent_key: AGENT_KEY,
        request_id: String(args.request_id),
      });
    
      const result = (await fetchJSON(
        `${API_BASE}/permission?${params.toString()}`
      )) as { status?: string; error?: string };
    
      if (result.error) {
        return `Failed to check permission: ${result.error}`;
      }
    
      return `Permission status: ${result.status}`;
    }
  • Schema definition for the check_permission tool. Defines the tool name, description, and input schema requiring a 'request_id' (number) parameter.
    {
      name: "check_permission",
      description:
        "Check the status of a previously submitted permission request. Returns 'pending', 'approved', or 'denied'.",
      inputSchema: {
        type: "object" as const,
        properties: {
          request_id: {
            type: "number",
            description: "The request ID returned from request_permission",
          },
        },
        required: ["request_id"],
      },
    },
  • Registration of the check_permission tool in the tools/call handler switch statement. Routes the 'check_permission' tool name to the handleCheckPermission function with the appropriate type cast.
    case "check_permission":
      resultText = await handleCheckPermission(
        toolArgs as { request_id: number }
      );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses return format and status values but does not mention potential error responses or side effects. Adequate for a simple read-only check, but could add more behavioral details.

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?

Three clear, informative sentences with no wasted words. Important information (purpose, usage, constraint) is presented efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage context, return format, and a constraint. Lacks error handling details but is largely complete for a polling tool without an output schema.

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?

Schema already describes the request_id parameter fully. The description reiterates the need for a valid request_id but does not add new semantic details beyond the schema. Baseline 3 due to 100% schema coverage.

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?

Clearly states the tool checks status of a permission request and returns a JSON object with specific status values. Distinguishes itself from siblings like request_permission by focusing on checking results.

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

Usage Guidelines5/5

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

Explicitly says to use after request_permission and to poll for decisions. Also states a negative condition: do not call without a valid request_id, which provides clear when-not guidance.

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

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