Skip to main content
Glama
yusuferenkt

MCP JSON Database Server

by yusuferenkt

verify_token

Validate JWT tokens to authenticate users and secure access to JSON database operations, ensuring only authorized interactions with project tracking, user management, and analytics features.

Instructions

JWT token'ın geçerliliğini kontrol eder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesJWT token

Implementation Reference

  • The execution handler for the 'verify_token' tool within the CallToolRequestSchema switch statement. It extracts the token from arguments, calls verifyToken helper, and returns success with decoded user data or error message.
    case 'verify_token': {
      const { token } = args;
      
      try {
        const decoded = verifyToken(token);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({ 
              success: true, 
              message: 'Token geçerli',
              user: decoded
            })
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({ success: false, message: error.message })
          }]
        };
      }
    }
  • src/index.js:97-106 (registration)
    Registration of the 'verify_token' tool in the tools list returned by ListToolsRequestHandler, including name, description, and input schema definition.
      name: 'verify_token',
      description: 'JWT token\'ın geçerliliğini kontrol eder',
      inputSchema: {
        type: 'object',
        properties: {
          token: { type: 'string', description: 'JWT token' }
        },
        required: ['token']
      }
    },
  • Input schema definition for the 'verify_token' tool, specifying the required 'token' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        token: { type: 'string', description: 'JWT token' }
      },
      required: ['token']
  • Helper function verifyToken that performs the core JWT token verification using jsonwebtoken.verify and throws an error on invalid tokens.
    export function verifyToken(token) {
        try {
            return jwt.verify(token, JWT_SECRET);
        } catch (error) {
            throw new Error('Geçersiz token');
        }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool checks token validity but doesn't disclose behavioral traits like what happens on success/failure (e.g., returns boolean, error messages), whether it performs network calls, rate limits, or side effects. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence in Turkish, front-loaded with the core purpose. It's appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on return values (e.g., success/failure indicators), error handling, or operational context, making it inadequate for reliable agent use without additional assumptions.

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 description coverage is 100%, with the parameter 'token' documented as 'JWT token'. The description adds no additional meaning beyond this, such as format details or examples. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'JWT token'ın geçerliliğini kontrol eder' (checks the validity of a JWT token) states a clear verb ('kontrol eder' - checks/verifies) and resource ('JWT token'), but it's vague about what 'validity' means (e.g., signature verification, expiration check, claims validation). It doesn't distinguish from siblings, though no obvious verification siblings exist in the list.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing a token), exclusions, or related tools like 'login' or authentication flows, leaving usage context implied but unspecified.

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/yusuferenkt/mcp-database'

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